Transmitting a physical downlink shared channel after losing uplink synchronization

ABSTRACT

Apparatuses, methods, and systems are disclosed for transmitting a physical downlink shared channel after losing uplink synchronization. One method includes: transmitting first downlink control information that schedules a physical downlink control channel order; transmitting second downlink control information that schedules a physical downlink shared channel transmission; transmitting the physical downlink control channel order based on the first downlink control information; transmitting the physical downlink shared channel transmission based on the second downlink control information, wherein the physical downlink control channel order and at least a portion of the physical downlink shared channel transmission are transmitted after a remote unit loses an uplink synchronization and before the remote unit completes a physical random access channel procedure.

FIELD

The subject matter disclosed herein relates generally to wirelesscommunications and more particularly relates to transmitting a physicaldownlink shared channel after losing uplink synchronization.

BACKGROUND

The following abbreviations are herewith defined, at least some of whichare referred to within the following description: Third GenerationPartnership Project (“3GPP”), 5^(th) Generation (“5G”),Positive-Acknowledgment (“ACK”), Access Point (“AP”), Autonomous Uplink(“AUL”), Binary Phase Shift Keying (“BPSK”), Buffer Status Report(“BSR”), Cell-RNTI (“C-RNTI”), Carrier Aggregation (“CA”), Clear ChannelAssessment (“CCA”), Common Control Channel (“CCCH”), Cyclic DelayDiversity (“CDD”), Code Division Multiple Access (“CDMA”), ControlElement (“CE”), Closed-Loop (“CL”), Coordinated Multipoint (“CoMP”),Cyclic Prefix (“CP”), Cyclical Redundancy Check (“CRC”), Channel StateInformation (“CSI”), Common Search Space (“CSS”), Control Resource Set(“CORESET”), Discrete Fourier Transform Spread (“DFTS”), DownlinkControl Information (“DCI”), Downlink (“DL”), Demodulation ReferenceSignal (“DMRS”), Data Volume and Power Headroom Report (“DPR”), DownlinkPilot Time Slot (“DwPTS”), Enhanced Clear Channel Assessment (“eCCA”),Enhanced Mobile Broadband (“eMBB”), Evolved Node B (“eNB”), EffectiveIsotropic Radiated Power (“EIRP”), European Telecommunications StandardsInstitute (“ETSI”), Frame Based Equipment (“FBE”), Frequency DivisionDuplex (“FDD”), Frequency Division Multiple Access (“FDMA”), FrequencyDivision Orthogonal Cover Code (“FD-OCC”), General Packet Radio Services(“GPRS”), Guard Period (“GP”), Global System for Mobile Communications(“GSM”), Hybrid Automatic Repeat Request (“HARQ”), International MobileTelecommunications (“IMT”), Internet-of-Things (“IoT”), Layer 2 (“L2”),Licensed Assisted Access (“LAA”), Load Based Equipment (“LBE”),Listen-Before-Talk (“LBT”), Logical Channel (“LCH”), Logical ChannelIdentity (“LCD”), Logical Channel Prioritization (“LCP”), Long TermEvolution (“LTE”), Multiple Access (“MA”), Medium Access Control(“MAC”), Multimedia Broadcast Multicast Services (“MBMS”), ModulationCoding

Scheme (“MCS”), Machine Type Communication (“MTC”), massive MTC(“mMTC”), Multiple Input Multiple Output (“MIMO”), Maximum PowerReduction (“MPR”), Multi User Shared Access (“MUSA”), Narrowband (“NB”),Negative-Acknowledgment (“NACK”) or (“NAK”), Next Generation Node B(“gNB”), Non-Orthogonal Multiple Access (“NOMA”), New Radio (“NR”),Orthogonal Frequency Division Multiplexing (“OFDM”), Open-Loop (“OL”),Power Angular Spectrum (“PAS”), Power Control (“PC”), Primary Cell(“PCell”), Primary Secondary Cell (“PSCell”), Physical Broadcast Channel(“PBCH”), Physical Downlink Control Channel (“PDCCH”), Packet DataConvergence Protocol (“PDCP”), Physical Downlink Shared Channel(“PDSCH”), Pattern Division Multiple Access (“PDMA”), Physical HybridARQ Indicator Channel (“PHICH”), Power Headroom (“PH”), Power HeadroomReport (“PHR”), Physical Layer (“PHY”), Physical Random Access Channel(“PRACH”), Physical Resource Block (“PRB”), Physical Uplink ControlChannel (“PUCCH”), Physical Uplink Shared Channel (“PUSCH”), QuasiCo-Located (“QCL”), Quality of Service (“QoS”), Quadrature Phase ShiftKeying (“QPSK”), Radio Access Network (“RAN”), Radio Access Technology(“RAT”), Resource Block Assignment (“RBA”), Radio Resource Control(“RRC”), Random Access Procedure (“RACH”), Random Access Response(“RAR”), Radio Link Control (“RLC”), Radio Network Temporary Identifier(“RNTI”), Reference Signal (“RS”), Remaining Minimum System Information(“RMSI”), Resource Spread Multiple Access (“RSMA”), Reference SignalReceived Power (“RSRP”), Round Trip Time (“RTT”), Receive (“RX”), SparseCode Multiple Access (“SCMA”), Scheduling Request (“SR”), SoundingReference Signal (“SRS”), Single Carrier Frequency Division MultipleAccess (“SC-FDMA”), Secondary Cell (“SCell”), Shared Channel (“SCH”),Sub-carrier Spacing (“SCS”), Service Data Unit (“SDU”),Signal-to-Interference-Plus-Noise Ratio (“SINR”), System InformationBlock (“SIB”), Scheduling Request (“SR”), Synchronization Signal (“SS”),Scheduled Uplink (“SUL”), Timing Alignment Timer (“TAT”), TransportBlock (“TB”), Transport Block Size (“TBS”), Time-Division Duplex(“TDD”), Time Division Multiplex (“TDM”), Time Division Orthogonal CoverCode (“TD-OCC”), Transmission Power Control (“TPC”), TransmissionReception Point (“TRP”), Transmission Time Interval (“TTI”), Transmit(“TX”), Uplink Control Information (“UCI”), User Entity/Equipment(Mobile Terminal) (“UE”), Uplink (“UL”), Universal MobileTelecommunications System (“UMTS”), Uplink Pilot Time Slot (“UpPTS”),Ultra-reliability and Low-latency Communications (“URLLC”), andWorldwide Interoperability for Microwave Access (“WiMAX”).

In certain wireless communications networks, a physical downlink sharedchannel transmission may be made. In such networks, a timing of thistransmission may depend on a remote unit status.

BRIEF SUMMARY

Methods for transmitting a physical downlink shared channel after losinguplink synchronization are disclosed. Apparatuses and systems alsoperform the functions of the apparatus. One embodiment of a methodincludes transmitting first downlink control information that schedulesa physical downlink control channel order. In some embodiments, themethod includes transmitting second downlink control information thatschedules a physical downlink shared channel transmission. In certainembodiments, the method includes transmitting the physical downlinkcontrol channel order based on the first downlink control information.In various embodiments, the method includes transmitting the physicaldownlink shared channel transmission based on the second downlinkcontrol information. In such embodiments, the physical downlink controlchannel order and at least a portion of the physical downlink sharedchannel transmission are transmitted after a remote unit loses an uplinksynchronization and before the remote unit completes a physical randomaccess channel procedure.

One apparatus for transmitting a physical downlink shared channel afterlosing uplink synchronization includes a transmitter that: transmitsfirst downlink control information that schedules a physical downlinkcontrol channel order; transmits second downlink control informationthat schedules a physical downlink shared channel transmission;transmits the physical downlink control channel order based on the firstdownlink control information; and transmits the physical downlink sharedchannel transmission based on the second downlink control information.In such embodiments, the physical downlink control channel order and atleast a portion of the physical downlink shared channel transmission aretransmitted after a remote unit loses an uplink synchronization andbefore the remote unit completes a physical random access channelprocedure.

One method for receiving a physical downlink shared channel after losinguplink synchronization includes receiving first downlink controlinformation that schedules a physical downlink control channel order. Insome embodiments, the method includes receiving second downlink controlinformation that schedules a physical downlink shared channeltransmission. In certain embodiments, the method includes receiving thephysical downlink control channel order based on the first downlinkcontrol information. In various embodiments, the method includesreceiving the physical downlink shared channel transmission based on thesecond downlink control information. In such embodiments, the physicaldownlink control channel order and at least a portion of the physicaldownlink shared channel transmission are received after a remote unitloses an uplink synchronization and before the remote unit completes aphysical random access channel procedure.

One apparatus for receiving a physical downlink shared channel afterlosing uplink synchronization includes a receiver that: receives firstdownlink control information that schedules a physical downlink controlchannel order; receives second downlink control information thatschedules a physical downlink shared channel transmission; receives thephysical downlink control channel order based on the first downlinkcontrol information; and receives the physical downlink shared channeltransmission based on the second downlink control information. In suchembodiments, the physical downlink control channel order and at least aportion of the physical downlink shared channel transmission arereceived after a remote unit loses an uplink synchronization and beforethe remote unit completes a physical random access channel procedure.

One method for transmitting a physical downlink shared channel afterlosing uplink synchronization includes transmitting a physical downlinkcontrol channel order. In some embodiments, the method includestransmitting a physical downlink shared channel transmission. In suchembodiments, the physical downlink control channel order and at least aportion of the physical downlink shared channel transmission aretransmitted after a remote unit loses an uplink synchronization andbefore the remote unit completes a physical random access channelprocedure. In certain embodiments, the method includes receivingfeedback information corresponding to the physical downlink sharedchannel transmission.

One apparatus for transmitting a physical downlink shared channel afterlosing uplink synchronization includes a transmitter that: transmits aphysical downlink control channel order; and transmits a physicaldownlink shared channel transmission. In such embodiments, the physicaldownlink control channel order and at least a portion of the physicaldownlink shared channel transmission are transmitted after a remote unitloses an uplink synchronization and before the remote unit completes aphysical random access channel procedure. In various embodiments, theapparatus includes a receiver that receives feedback informationcorresponding to the physical downlink shared channel transmission.

One method for receiving a physical downlink shared channel after losinguplink synchronization includes receiving a physical downlink controlchannel order. In some embodiments, the method includes receiving aphysical downlink shared channel transmission. In such embodiments, thephysical downlink control channel order and at least a portion of thephysical downlink shared channel transmission are received after aremote unit loses an uplink synchronization and before the remote unitcompletes a physical random access channel procedure. In certainembodiments, the method includes transmitting feedback informationcorresponding to the physical downlink shared channel transmission.

One apparatus for receiving a physical downlink shared channel afterlosing uplink synchronization includes a receiver that: receives aphysical downlink control channel order; and receives a physicaldownlink shared channel transmission. In such embodiments, the physicaldownlink control channel order and at least a portion of the physicaldownlink shared channel transmission are received after a remote unitloses an uplink synchronization and before the remote unit completes aphysical random access channel procedure. In some embodiments, theapparatus includes a transmitter that transmits feedback informationcorresponding to the physical downlink shared channel transmission.

One method for transmitting downlink data after losing uplinksynchronization includes determining a remote unit that is to receivedownlink data. In some embodiments, the method includes transmitting thedownlink data with a random access response. In such embodiments, thedownlink data is transmitted after the remote unit loses an uplinksynchronization and before the remote unit completes a physical randomaccess channel procedure. In certain embodiments, the method includesreceiving feedback information corresponding to the downlink data.

One apparatus for transmitting downlink data after losing uplinksynchronization includes a processor that determines a remote unit thatis to receive downlink data. In various embodiments, the apparatusincludes a transmitter that transmits the downlink data with a randomaccess response. In such embodiments, the downlink data is transmittedafter the remote unit loses an uplink synchronization and before theremote unit completes a physical random access channel procedure. Incertain embodiments, the apparatus includes a receiver that receivesfeedback information corresponding to the downlink data.

One method for receiving downlink data after losing uplinksynchronization includes receiving downlink data with a random accessresponse. In such embodiments, the downlink data is received after aremote unit loses an uplink synchronization and before the remote unitcompletes a physical random access channel procedure. In someembodiments, the method includes transmitting feedback informationcorresponding to the downlink data.

One apparatus for receiving downlink data after losing uplinksynchronization includes a receiver that receives downlink data with arandom access response. In such embodiments, the downlink data isreceived after a remote unit loses an uplink synchronization and beforethe remote unit completes a physical random access channel procedure. Invarious embodiments, the apparatus includes a transmitter that transmitsfeedback information corresponding to the downlink data.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described abovewill be rendered by reference to specific embodiments that areillustrated in the appended drawings. Understanding that these drawingsdepict only some embodiments and are not therefore to be considered tobe limiting of scope, the embodiments will be described and explainedwith additional specificity and detail through the use of theaccompanying drawings, in which:

FIG. 1 is a schematic block diagram illustrating one embodiment of awireless communication system for transmitting and/or receiving aphysical downlink shared channel after losing uplink synchronization;

FIG. 2 is a schematic block diagram illustrating one embodiment of anapparatus that may be used for receiving a physical downlink sharedchannel after losing uplink synchronization;

FIG. 3 is a schematic block diagram illustrating one embodiment of anapparatus that may be used for transmitting a physical downlink sharedchannel after losing uplink synchronization;

FIG. 4 is a schematic block diagram illustrating one embodiment ofcommunications between a UE and a gNB;

FIG. 5 is a schematic block diagram illustrating another embodiment ofcommunications between a UE and a gNB;

FIG. 6 is a schematic block diagram illustrating a further embodiment ofcommunications between a UE and a gNB;

FIG. 7 is a schematic block diagram illustrating yet another embodimentof communications between a UE and a gNB;

FIG. 8 is a schematic block diagram illustrating an additionalembodiment of communications between a UE and a gNB;

FIG. 9 is a schematic block diagram illustrating yet a furtherembodiment of communications between a UE and a gNB;

FIG. 10 is a flow chart diagram illustrating one embodiment of a methodfor transmitting a physical downlink shared channel after losing uplinksynchronization;

FIG. 11 is a flow chart diagram illustrating one embodiment of a methodfor receiving a physical downlink shared channel after losing uplinksynchronization;

FIG. 12 is a flow chart diagram illustrating another embodiment of amethod for transmitting a physical downlink shared channel after losinguplink synchronization;

FIG. 13 is a flow chart diagram illustrating another embodiment of amethod for receiving a physical downlink shared channel after losinguplink synchronization;

FIG. 14 is a flow chart diagram illustrating one embodiment of a methodfor transmitting downlink data; and

FIG. 15 is a flow chart diagram illustrating one embodiment of a methodfor receiving downlink data.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of theembodiments may be embodied as a system, apparatus, method, or programproduct. Accordingly, embodiments may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,embodiments may take the form of a program product embodied in one ormore computer readable storage devices storing machine readable code,computer readable code, and/or program code, referred hereafter as code.The storage devices may be tangible, non-transitory, and/ornon-transmission. The storage devices may not embody signals. In acertain embodiment, the storage devices only employ signals foraccessing code.

Certain of the functional units described in this specification may belabeled as modules, in order to more particularly emphasize theirimplementation independence. For example, a module may be implemented asa hardware circuit comprising custom very-large-scale integration(“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such aslogic chips, transistors, or other discrete components. A module mayalso be implemented in programmable hardware devices such as fieldprogrammable gate arrays, programmable array logic, programmable logicdevices or the like.

Modules may also be implemented in code and/or software for execution byvarious types of processors. An identified module of code may, forinstance, include one or more physical or logical blocks of executablecode which may, for instance, be organized as an object, procedure, orfunction. Nevertheless, the executables of an identified module need notbe physically located together, but may include disparate instructionsstored in different locations which, when joined logically together,include the module and achieve the stated purpose for the module.

Indeed, a module of code may be a single instruction, or manyinstructions, and may even be distributed over several different codesegments, among different programs, and across several memory devices.Similarly, operational data may be identified and illustrated hereinwithin modules, and may be embodied in any suitable form and organizedwithin any suitable type of data structure. The operational data may becollected as a single data set, or may be distributed over differentlocations including over different computer readable storage devices.Where a module or portions of a module are implemented in software, thesoftware portions are stored on one or more computer readable storagedevices.

Any combination of one or more computer readable medium may be utilized.The computer readable medium may be a computer readable storage medium.The computer readable storage medium may be a storage device storing thecode. The storage device may be, for example, but not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, holographic,micromechanical, or semiconductor system, apparatus, or device, or anysuitable combination of the foregoing.

More specific examples (a non-exhaustive list) of the storage devicewould include the following: an electrical connection having one or morewires, a portable computer diskette, a hard disk, a random access memory(“RAM”), a read-only memory (“ROM”), an erasable programmable read-onlymemory (“EPROM” or Flash memory), a portable compact disc read-onlymemory (“CD-ROM”), an optical storage device, a magnetic storage device,or any suitable combination of the foregoing. In the context of thisdocument, a computer readable storage medium may be any tangible mediumthat can contain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

Code for carrying out operations for embodiments may be any number oflines and may be written in any combination of one or more programminglanguages including an object oriented programming language such asPython, Ruby, Java, Smalltalk, C++, or the like, and conventionalprocedural programming languages, such as the “C” programming language,or the like, and/or machine languages such as assembly languages. Thecode may execute entirely on the user's computer, partly on the user'scomputer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through any type of network, includinga local area network (“LAN”) or a wide area network (“WAN”), or theconnection may be made to an external computer (for example, through theInternet using an Internet Service Provider).

Reference throughout this specification to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment. Thus, appearances of the phrases“in one embodiment,” “in an embodiment,” and similar language throughoutthis specification may, but do not necessarily, all refer to the sameembodiment, but mean “one or more but not all embodiments” unlessexpressly specified otherwise. The terms “including,” “comprising,”“having,” and variations thereof mean “including but not limited to,”unless expressly specified otherwise. An enumerated listing of itemsdoes not imply that any or all of the items are mutually exclusive,unless expressly specified otherwise. The terms “a,” “an,” and “the”also refer to “one or more” unless expressly specified otherwise.

Furthermore, the described features, structures, or characteristics ofthe embodiments may be combined in any suitable manner. In the followingdescription, numerous specific details are provided, such as examples ofprogramming, software modules, user selections, network transactions,database queries, database structures, hardware modules, hardwarecircuits, hardware chips, etc., to provide a thorough understanding ofembodiments. One skilled in the relevant art will recognize, however,that embodiments may be practiced without one or more of the specificdetails, or with other methods, components, materials, and so forth. Inother instances, well-known structures, materials, or operations are notshown or described in detail to avoid obscuring aspects of anembodiment.

Aspects of the embodiments are described below with reference toschematic flowchart diagrams and/or schematic block diagrams of methods,apparatuses, systems, and program products according to embodiments. Itwill be understood that each block of the schematic flowchart diagramsand/or schematic block diagrams, and combinations of blocks in theschematic flowchart diagrams and/or schematic block diagrams, can beimplemented by code. The code may be provided to a processor of ageneral purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the schematic flowchartdiagrams and/or schematic block diagrams block or blocks.

The code may also be stored in a storage device that can direct acomputer, other programmable data processing apparatus, or other devicesto function in a particular manner, such that the instructions stored inthe storage device produce an article of manufacture includinginstructions which implement the function/act specified in the schematicflowchart diagrams and/or schematic block diagrams block or blocks.

The code may also be loaded onto a computer, other programmable dataprocessing apparatus, or other devices to cause a series of operationalsteps to be performed on the computer, other programmable apparatus orother devices to produce a computer implemented process such that thecode which execute on the computer or other programmable apparatusprovide processes for implementing the functions/acts specified in theflowchart and/or block diagram block or blocks.

The schematic flowchart diagrams and/or schematic block diagrams in theFigures illustrate the architecture, functionality, and operation ofpossible implementations of apparatuses, systems, methods and programproducts according to various embodiments. In this regard, each block inthe schematic flowchart diagrams and/or schematic block diagrams mayrepresent a module, segment, or portion of code, which includes one ormore executable instructions of the code for implementing the specifiedlogical function(s).

It should also be noted that, in some alternative implementations, thefunctions noted in the block may occur out of the order noted in theFigures. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. Other steps and methods may be conceived that are equivalentin function, logic, or effect to one or more blocks, or portionsthereof, of the illustrated Figures.

Although various arrow types and line types may be employed in theflowchart and/or block diagrams, they are understood not to limit thescope of the corresponding embodiments. Indeed, some arrows or otherconnectors may be used to indicate only the logical flow of the depictedembodiment. For instance, an arrow may indicate a waiting or monitoringperiod of unspecified duration between enumerated steps of the depictedembodiment. It will also be noted that each block of the block diagramsand/or flowchart diagrams, and combinations of blocks in the blockdiagrams and/or flowchart diagrams, can be implemented by specialpurpose hardware-based systems that perform the specified functions oracts, or combinations of special purpose hardware and code.

The description of elements in each figure may refer to elements ofproceeding figures. Like numbers refer to like elements in all figures,including alternate embodiments of like elements.

FIG. 1 depicts an embodiment of a wireless communication system 100 fortransmitting and/or receiving a physical downlink shared channel afterlosing uplink synchronization. In one embodiment, the wirelesscommunication system 100 includes remote units 102 and network units104. Even though a specific number of remote units 102 and network units104 are depicted in FIG. 1, one of skill in the art will recognize thatany number of remote units 102 and network units 104 may be included inthe wireless communication system 100.

In one embodiment, the remote units 102 may include computing devices,such as desktop computers, laptop computers, personal digital assistants(“PDAs”), tablet computers, smart phones, smart televisions (e.g.,televisions connected to the Internet), set-top boxes, game consoles,security systems (including security cameras), vehicle on-boardcomputers, network devices (e.g., routers, switches, modems), aerialvehicles, drones, or the like. In some embodiments, the remote units 102include wearable devices, such as smart watches, fitness bands, opticalhead-mounted displays, or the like. Moreover, the remote units 102 maybe referred to as subscriber units, mobiles, mobile stations, users,terminals, mobile terminals, fixed terminals, subscriber stations, UE,user terminals, a device, or by other terminology used in the art. Theremote units 102 may communicate directly with one or more of thenetwork units 104 via UL communication signals.

The network units 104 may be distributed over a geographic region. Incertain embodiments, a network unit 104 may also be referred to as anaccess point, an access terminal, a base, a base station, a Node-B, aneNB, a gNB, a Home Node-B, a relay node, a device, a core network, anaerial server, a radio access node, an AP, NR, or by any otherterminology used in the art. The network units 104 are generally part ofa radio access network that includes one or more controllerscommunicably coupled to one or more corresponding network units 104. Theradio access network is generally communicably coupled to one or morecore networks, which may be coupled to other networks, like the Internetand public switched telephone networks, among other networks. These andother elements of radio access and core networks are not illustrated butare well known generally by those having ordinary skill in the art.

In one implementation, the wireless communication system 100 iscompliant with NR protocols standardized in 3GPP, wherein the networkunit 104 transmits using an OFDM modulation scheme on the DL and theremote units 102 transmit on the UL using a SC-FDMA scheme or an OFDMscheme. More generally, however, the wireless communication system 100may implement some other open or proprietary communication protocol, forexample, WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants,CDMA2000, Bluetooth®, ZigBee, Sigfoxx, among other protocols. Thepresent disclosure is not intended to be limited to the implementationof any particular wireless communication system architecture orprotocol.

The network units 104 may serve a number of remote units 102 within aserving area, for example, a cell or a cell sector via a wirelesscommunication link. The network units 104 transmit DL communicationsignals to serve the remote units 102 in the time, frequency, and/orspatial domain.

In certain embodiments, a network unit 104 may be used for transmittinga physical downlink shared channel after losing uplink synchronization.In various embodiments, the network unit 104 may transmit first downlinkcontrol information that schedules a physical downlink control channelorder. In some embodiments, the network unit 104 may transmit seconddownlink control information that schedules a physical downlink sharedchannel transmission. In certain embodiments, the network unit 104 maytransmit the physical downlink control channel order based on the firstdownlink control information. In various embodiments, the network unit104 may transmit the physical downlink shared channel transmission basedon the second downlink control information. In such embodiments, thephysical downlink control channel order and at least a portion of thephysical downlink shared channel transmission are transmitted after aremote unit 102 loses an uplink synchronization and before the remoteunit 102 completes a physical random access channel procedure.Accordingly, the network unit 104 may be used for transmitting aphysical downlink shared channel after losing uplink synchronization.

In one embodiment, a remote unit 102 may be used for receiving aphysical downlink shared channel after losing uplink synchronization. Incertain embodiments, the remote unit 102 may receive first downlinkcontrol information that schedules a physical downlink control channelorder. In some embodiments, the remote unit 102 may receive seconddownlink control information that schedules a physical downlink sharedchannel transmission. In certain embodiments, the remote unit 102 mayreceive the physical downlink control channel order based on the firstdownlink control information. In various embodiments, the remote unit102 may receive the physical downlink shared channel transmission basedon the second downlink control information. In such embodiments, thephysical downlink control channel order and at least a portion of thephysical downlink shared channel transmission are received after theremote unit 102 loses an uplink synchronization and before the remoteunit 102 completes a physical random access channel procedure.Accordingly, the remote unit 102 may be used for receiving a physicaldownlink shared channel after losing uplink synchronization.

In certain embodiments, a network unit 104 may be used for transmittinga physical downlink shared channel after losing uplink synchronization.In various embodiments, the network unit 104 may transmit a physicaldownlink control channel order. In some embodiments, the network unit104 may transmit a physical downlink shared channel transmission. Insuch embodiments, the physical downlink control channel order and atleast a portion of the physical downlink shared channel transmission aretransmitted after a remote unit 102 loses an uplink synchronization andbefore the remote unit 102 completes a physical random access channelprocedure. In certain embodiments, the network unit 104 may receivefeedback information corresponding to the physical downlink sharedchannel transmission. Accordingly, the network unit 104 may be used fortransmitting a physical downlink shared channel after losing uplinksynchronization.

In one embodiment, a remote unit 102 may be used for receiving aphysical downlink shared channel after losing uplink synchronization. Incertain embodiments, the remote unit 102 may receive a physical downlinkcontrol channel order. In some embodiments, the remote unit 102 mayreceive a physical downlink shared channel transmission. In suchembodiments, the physical downlink control channel order and at least aportion of the physical downlink shared channel transmission arereceived after the remote unit 102 loses an uplink synchronization andbefore the remote unit 102 completes a physical random access channelprocedure. In certain embodiments, the remote unit 102 may transmitfeedback information corresponding to the physical downlink sharedchannel transmission. Accordingly, the remote unit 102 may be used forreceiving a physical downlink shared channel after losing uplinksynchronization.

In certain embodiments, a network unit 104 may be used for transmittingdownlink data after losing uplink synchronization. In variousembodiments, the network unit 104 may determine a remote unit 102 thatis to receive downlink data. In some embodiments, the network unit 104may transmit the downlink data with a random access response. In suchembodiments, the downlink data is transmitted after the remote unit 102loses an uplink synchronization and before the remote unit 102 completesa physical random access channel procedure. In certain embodiments, thenetwork unit 104 may receive feedback information corresponding to thedownlink data. Accordingly, the network unit 104 may be used fortransmitting downlink data after losing uplink synchronization.

In one embodiment, a remote unit 102 may be used for receiving downlinkdata after losing uplink synchronization. In certain embodiments, theremote unit 102 may receive downlink data with a random access response.In such embodiments, the downlink data is received after the remote unit102 loses an uplink synchronization and before the remote unit 102completes a physical random access channel procedure. In someembodiments, the remote unit 102 may transmit feedback informationcorresponding to the downlink data. Accordingly, the remote unit 102 maybe used for receiving downlink data after losing uplink synchronization.

FIG. 2 depicts one embodiment of an apparatus 200 that may be used forreceiving a physical downlink shared channel after losing uplinksynchronization. The apparatus 200 includes one embodiment of the remoteunit 102. Furthermore, the remote unit 102 may include a processor 202,a memory 204, an input device 206, a display 208, a transmitter 210, anda receiver 212. In some embodiments, the input device 206 and thedisplay 208 are combined into a single device, such as a touchscreen. Incertain embodiments, the remote unit 102 may not include any inputdevice 206 and/or display 208. In various embodiments, the remote unit102 may include one or more of the processor 202, the memory 204, thetransmitter 210, and the receiver 212, and may not include the inputdevice 206 and/or the display 208.

The processor 202, in one embodiment, may include any known controllercapable of executing computer-readable instructions and/or capable ofperforming logical operations. For example, the processor 202 may be amicrocontroller, a microprocessor, a central processing unit (“CPU”), agraphics processing unit (“GPU”), an auxiliary processing unit, a fieldprogrammable gate array (“FPGA”), or similar programmable controller. Insome embodiments, the processor 202 executes instructions stored in thememory 204 to perform the methods and routines described herein. Theprocessor 202 is communicatively coupled to the memory 204, the inputdevice 206, the display 208, the transmitter 210, and the receiver 212.

The memory 204, in one embodiment, is a computer readable storagemedium. In some embodiments, the memory 204 includes volatile computerstorage media. For example, the memory 204 may include a RAM, includingdynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or staticRAM (“SRAM”). In some embodiments, the memory 204 includes non-volatilecomputer storage media. For example, the memory 204 may include a harddisk drive, a flash memory, or any other suitable non-volatile computerstorage device. In some embodiments, the memory 204 includes bothvolatile and non-volatile computer storage media. In some embodiments,the memory 204 also stores program code and related data, such as anoperating system or other controller algorithms operating on the remoteunit 102.

The input device 206, in one embodiment, may include any known computerinput device including a touch panel, a button, a keyboard, a stylus, amicrophone, or the like. In some embodiments, the input device 206 maybe integrated with the display 208, for example, as a touchscreen orsimilar touch-sensitive display. In some embodiments, the input device206 includes a touchscreen such that text may be input using a virtualkeyboard displayed on the touchscreen and/or by handwriting on thetouchscreen. In some embodiments, the input device 206 includes two ormore different devices, such as a keyboard and a touch panel.

The display 208, in one embodiment, may include any known electronicallycontrollable display or display device. The display 208 may be designedto output visual, audible, and/or haptic signals. In some embodiments,the display 208 includes an electronic display capable of outputtingvisual data to a user. For example, the display 208 may include, but isnot limited to, an LCD display, an LED display, an OLED display, aprojector, or similar display device capable of outputting images, text,or the like to a user. As another, non-limiting, example, the display208 may include a wearable display such as a smart watch, smart glasses,a heads-up display, or the like. Further, the display 208 may be acomponent of a smart phone, a personal digital assistant, a television,a table computer, a notebook (laptop) computer, a personal computer, avehicle dashboard, or the like.

In certain embodiments, the display 208 includes one or more speakersfor producing sound. For example, the display 208 may produce an audiblealert or notification (e.g., a beep or chime). In some embodiments, thedisplay 208 includes one or more haptic devices for producingvibrations, motion, or other haptic feedback. In some embodiments, allor portions of the display 208 may be integrated with the input device206. For example, the input device 206 and display 208 may form atouchscreen or similar touch-sensitive display. In other embodiments,the display 208 may be located near the input device 206.

The transmitter 210 is used to provide UL communication signals to thenetwork unit 104 and the receiver 212 is used to receive DLcommunication signals from the network unit 104, as described herein. Insome embodiments, the receiver 212: receives first downlink controlinformation that schedules a physical downlink control channel order;receives second downlink control information that schedules a physicaldownlink shared channel transmission; receives the physical downlinkcontrol channel order based on the first downlink control information;and receives the physical downlink shared channel transmission based onthe second downlink control information. In such embodiments, thephysical downlink control channel order and at least a portion of thephysical downlink shared channel transmission are received after aremote unit 102 loses an uplink synchronization and before the remoteunit 102 completes a physical random access channel procedure.

In various embodiments, the receiver 212: receives a physical downlinkcontrol channel order; and receives a physical downlink shared channeltransmission. In such embodiments, the physical downlink control channelorder and at least a portion of the physical downlink shared channeltransmission are received after a remote unit 102 loses an uplinksynchronization and before the remote unit 102 completes a physicalrandom access channel procedure. In some embodiments, the transmitter210 transmits feedback information corresponding to the physicaldownlink shared channel transmission.

In certain embodiments, the receiver 212 receives downlink data with arandom access response. In such embodiments, the downlink data isreceived after a remote unit 102 loses an uplink synchronization andbefore the remote unit 102 completes a physical random access channelprocedure. In various embodiments, the transmitter 210 transmitsfeedback information corresponding to the downlink data. Although onlyone transmitter 210 and one receiver 212 are illustrated, the remoteunit 102 may have any suitable number of transmitters 210 and receivers212. The transmitter 210 and the receiver 212 may be any suitable typeof transmitters and receivers. In one embodiment, the transmitter 210and the receiver 212 may be part of a transceiver.

FIG. 3 depicts one embodiment of an apparatus 300 that may be used fortransmitting a physical downlink shared channel after losing uplinksynchronization. The apparatus 300 includes one embodiment of thenetwork unit 104. Furthermore, the network unit 104 may include aprocessor 302, a memory 304, an input device 306, a display 308, atransmitter 310, and a receiver 312. As may be appreciated, theprocessor 302, the memory 304, the input device 306, the display 308,the transmitter 310, and the receiver 312 may be substantially similarto the processor 202, the memory 204, the input device 206, the display208, the transmitter 210, and the receiver 212 of the remote unit 102,respectively.

In some embodiments, the transmitter 310: transmits first downlinkcontrol information that schedules a physical downlink control channelorder; transmits second downlink control information that schedules aphysical downlink shared channel transmission; transmits the physicaldownlink control channel order based on the first downlink controlinformation; and transmits the physical downlink shared channeltransmission based on the second downlink control information. In suchembodiments, the physical downlink control channel order and at least aportion of the physical downlink shared channel transmission aretransmitted after a remote unit 102 loses an uplink synchronization andbefore the remote unit 102 completes a physical random access channelprocedure.

In various embodiments, the transmitter 310: transmits a physicaldownlink control channel order; and transmits a physical downlink sharedchannel transmission. In such embodiments, the physical downlink controlchannel order and at least a portion of the physical downlink sharedchannel transmission are transmitted after a remote unit 102 loses anuplink synchronization and before the remote unit 102 completes aphysical random access channel procedure. In various embodiments, thereceiver 312 receives feedback information corresponding to the physicaldownlink shared channel transmission.

In certain embodiments, the processor 302 determines a remote unit 102that is to receive downlink data. In various embodiments, thetransmitter 310 transmits the downlink data with a random accessresponse. In such embodiments, the downlink data is transmitted afterthe remote unit loses an uplink synchronization and before the remoteunit 102 completes a physical random access channel procedure. Incertain embodiments, the receiver 312 receives feedback informationcorresponding to the downlink data. Although only one transmitter 310and one receiver 312 are illustrated, the network unit 104 may have anysuitable number of transmitters 310 and receivers 312. The transmitter310 and the receiver 312 may be any suitable type of transmitters andreceivers. In one embodiment, the transmitter 310 and the receiver 312may be part of a transceiver.

In certain embodiments, PDCCH order is a mechanism by which a gNB (orany RAN node like an eNB in LTE) orders a UE (e.g., remote unit 102) toinitiate PRACH. In some embodiments, a PDCCH order is sent in responseto a network unit 104 having DL data for the UE, but suspects that theUE is not UL Synchronized (e.g., because the TAT has expired). Invarious embodiments, by ordering the UE to perform a RACH procedure, thegNB may enable the UE to apply a timing advance before the UE is readyto send anything (e.g., HARQ feedback for any DL data) in the UL. Asshown in FIG. 4, it may take at least five message exchanges between theUE and the network unit 104 (e.g., gNB) to start sending first downlinkdata. This may take more message exchanges in an unlicensed spectrum dueto restrictions imposed by an LBT procedure. Accordingly, as may beappreciated, this large number of message exchanges may make DLtransmission resumption inefficient resulting in wasted time and/orexcessive UE battery consumption. Accordingly, even for a licensedspectrum, latency sensitive applications may operate inefficiently. Insome embodiments, a network unit 104 may have only one DL packet (e.g.,application layer signalling) to send and such an elaborate procedure toresume data transmission may be inefficient. As described herein,various communication sequences may be used to reduce suchinefficiencies while a UE is out of UL synchronization.

FIG. 4 is a schematic block diagram illustrating one embodiment ofcommunications 400 between a UE 402 (e.g., remote unit 102) and a gNB404 (e.g., network unit 104). The communications 400 illustrate that theUE 402 starts in an RRC connected state 406. After TAT expiration 408,the UE 402 loses an UL synchronization 410. At a time after the UE 402loses the UL synchronization 410, DL data arrives 412 at the gNB 404. Inresponse to the DL data arriving 412 at the gNB 404, the gNB 404transmits 414 a PDCCH order to the UE 402. Accordingly, the UE 402initiates a PRACH procedure by transmitting 416 a PRACH message 1 (e.g.,PRACH preamble) to the gNB 404. In response to receiving the PRACHmessage 1, the gNB 404 transmits 418 a random access response (e.g.,message 2) to the UE 402. At a time 420 after the gNB 404 transmits 418the random access response, the UE 402 has UL synchronization.Accordingly, the UE 402 transmits a PUSCH 422 to the gNB 404. As aresult of receiving the PUSCH 422, the gNB 404 transmits one or more DLTBs 424 based on the DL data that arrived 412 at the gNB 404. Inresponse to receiving the one or more DL TBs 424, the UE 402 transmitsfeedback 426 (e.g., HARQ-ACK, ACK/NACK) to the gNB 404 to indicatewhether the one or more DL TBs 424 were received correctly.

As illustrated in FIG. 4, in certain embodiments in the licensed medium(e.g., like 5G NR licensed bands), the system 100 (e.g., UE 402 and thegNB 404 together) may perform 4-5 message exchange to accomplish a firstdownlink data transmission at times in which the UE 402 is not ULsynchronized. Moreover, transmissions on an unlicensed medium, includingtransmission by the UE 402 and the network (e.g., gNB 404), may need tofollow an LBT procedure for each of those messages individually andindependently. As may be appreciated, the above inefficiency applies toa random access procedure as well as to downlink (e.g., PDSCH) anduplink (e.g., PUSCH) transmissions. Each of these transmissions mustfirst undergo a CCA procedure before the transmission can be made on theunlicensed spectrum. Thus, in certain configurations, many messageexchanges may be required for a first DL data packet at times in whichthe UE 402 is out of synchronisation, irrespective of being in thelicensed or the unlicensed band.

FIG. 5 is a schematic block diagram illustrating another embodiment ofcommunications 500 between a UE 502 (e.g., remote unit 102) and a gNB504 (e.g., network unit 104). The communications 500 illustrate that theUE 502 starts in an RRC connected state 506. After TAT expiration 508,the UE 502 loses an UL synchronization 510. At a time after the UE 502loses the UL synchronization 510, DL data arrives 512 at the gNB 504. Inresponse to the DL data arriving 512 at the gNB 504, the gNB 504transmits 514 a PDCCH order to the UE 502. In this embodiment, the PDCCHorder transmitted 514 to the UE 502 may be transmitted with one or moreDL TBs based on the DL data that arrived 512 at the gNB 504. Afterreceiving the PDCCH order, the UE 502 initiates a PRACH procedure bytransmitting 516 a PRACH message 1 (e.g., PRACH preamble) to the gNB504. In response to receiving the PRACH message 1, the gNB 504 transmits518 a random access response (e.g., message 2) to the UE 502. At a time520 after the gNB 504 transmits 518 the random access response, the UE502 has UL synchronization. Accordingly, the UE 502 transmits a PUSCH522 to the gNB 504. The PUSCH 522, in this embodiment, may betransmitted with feedback (e.g., HARQ-ACK, ACK/NACK) to the gNB 504 toindicate whether the one or more DL TBs were received correctly. Byusing this set of communications 500, DL data (e.g., one or more DL TBs)may be transmitted to the UE 502 faster than in other embodiments, suchas the embodiment described in FIG. 4.

In certain embodiment, the gNB 504 sends a DL TB (or more than one TBsin case of MIMO) along with the PDCCH order and the UE 502 sends theHARQ feedback as part of the PUSCH 522 transmission after getting ULtime aligned based on a TA command received in message 2. In someembodiments, the DL TB may be transmitted together (e.g., in the sameslot) with the PDCCH order.

In various embodiments, DCI carrying the PDCCH order may also carryscheduling information for the PDSCH carrying DL TB. In certainembodiments, a new DCI format may be used to signal presence of both aPDCCH order as well as downlink assignment. This new DCI format may havecontents of both PDCCH order as well as of downlink assignment (e.g.,those present in format 1_0). Some of the contents from format 1_0 maybe omitted to reduce the size of the new DCI format or to make it thesame and/or similar size to format 1_0. The content of this new DCIformat may resemble the content described herein. In one embodiment, theUE 502 monitors for this new DCI format only if an uplink timingalignment timer expires.

In some embodiments, the contents of DCI format 1_0 may be redesigned orrearranged in a way to include only the information necessary at timesin which both PDCCH order and a downlink assignment are present. In suchembodiment, a UE capability may indicate if the UE 502 is capable ofinterpreting the redesigned format 1_0. Further, if the network iscapable of transmitting such a redesigned format 1_0, the network (e.g.,gNB 504) may indicate this capability to the UE 502 (e.g., using RRCsignaling configuration). For example, the network may indicate that theDCI format 1_0 will be used in the redesigned way. In certainembodiments, the re-designed DCI format 1_0 is used only at times inwhich the UE 502 has lost UL synchronization.

In various embodiments, parsing and interpretation of DCI format 1_0that is redesigned may be done as described herein. For example, thefollowing information may be transmitted by means of the DCI format 1_0redesigned with CRC scrambled by C-RNTI, CS-RNTI, RNTI, or anew-RNTI: 1) Identifier for DCI formats—1 bit. The value of this bitfield is always set to 1, indicating a DL DCI format; 2) Legacy usage—1bit. A value of TRUE means that the rest of the fields in this DCI willbe interpreted exactly as in legacy DCI format 1_0 starting immediatelywith frequency domain resource assignment. A value of FALSE means thatthe rest of the fields in this DCI will be interpreted in a redesignedway as shown further. As may be appreciated, the use of TRUE and FALSEcould be used opposite that described herein. Moreover, this field maybe renamed to “new usage,” “combined usage,” or any suitable name; 3)Frequency domain resource assignment—┌log₂(N_(RB) ^(DL,BWP)(N_(RB)^(DL,BWP)+1)/2┐ bits. N_(RB) ^(DL,BWP) is the size of the active DLbandwidth part in case DCI format 1_0 is monitored in the UE specificsearch space and satisfying: the total number of different DCI sizesmonitored per slot is no more than 4 for the cell; and the total numberof different DCI sizes with C-RNTI monitored per slot is no more than 3for the cell, otherwise, N_(RB) ^(DL,BWP) is the size of the initial DLbandwidth part. As one other possibility NRBG bits are used instead of“Frequency domain resource assignment” if only resource allocation type0 is used as defined in TS 38.212-f20; 4) Random Access Preamble index—6bits according to ra-PreambleIndex in Subclause 5.1.2 of [8, TS38.321];5) UL/SUL indicator—1 bit. If the value of the “Random Access Preambleindex” is not all zeros and if the UE is configured with SUL in thecell, this field indicates which UL carrier in the cell to transmit thePRACH according to Table 7.3.1.1.1-1; otherwise, this field is reserved;6) SS/PBCH index—6 bits. If the value of the “Random Access Preambleindex” is not all zeros, this field indicates the SS/PBCH that shall beused to determine the RACH occasion for the PRACH transmission;otherwise, this field is reserved; 7) PRACH Mask index—4 bits. If thevalue of the “Random Access Preamble index” is not all zeros, this fieldindicates the RACH occasion associated with the SS/PBCH indicated by“SS/PBCH index” for the PRACH transmission, according to Subclause 5.1.1of [8, TS38.321]; otherwise, this field is reserved; 8) Time domainresource assignment—optionally present. Slot location for PDSCH may befixed or RRC configured relative to a selected PRACH occasion orrelative to a slot where PDCCH order DCI is transmitted. If present,network indicates a starting symbol within a slot and PDSCH duration (interms of # of symbols) depending on the DL TB size. If not present, inone possible embodiment, the PRACH and DL assignment (i.e. PDSCHreception) take place at the same point in time (subframe, symbol#) orare apart from each other by a value (e.g. in number of symbols) eitherdefined in specification or configured by higher layer like RRC; 9)VRB-to-PRB mapping—1 bit according to Table 7.3.1.1.2-33 of TS38.212-f20; 10) Modulation and coding scheme—5 bits as defined inSubclause 5.1.3 of [6, TS 38.214]; 10) New data indicator—not present;11) Redundancy version—not present; 12) HARQ process number—not present.Instead, in one embodiment, a fixed HARQ process ID is used which isknown to both the network and the UE by way of specification orconfigured by higher layer like RRC. If this reserved/fixed HARQ processID was being used already (when TAT is running at the time of receivinga PDCCH order), i.e., a non-empty HARQ buffer, then the HARQ buffershall be overwritten with the contents of the DL TB; 13) Downlinkassignment index; 14) TPC command for scheduled PUCCH—not present; 15)PUCCH resource indicator—3 bits as defined in Subclause 9.2.3 of [5, TS38.213]—in one embodiment this is present, in another embodiment this isnot present; 16) PDSCH-to-HARQ feedback timing indicator—optional. Ifnot present, PUCCH feedback after the DL-SCH could be based on a fixedtime location (e.g., offset). Otherwise, this may be signaled explicitlyin DCI format 1_0 for DL assignment.

In some embodiments, a PDCCH order DCI format 1_0 as defined in 3GPP TS38.212420 is used in a redesigned way (e.g., the CRC of the DCI format1_0 is scrambled by C-RNTI but the “Frequency domain resourceassignment” field has valid resource signaling, i.e., are not all ones).In such embodiments, the 10 reserved bits of the PDCCH order may be usedsuch that one of the 10 reserved bits indicates whether the new or oldformat 1_0 applies (e.g., if the 10 reserved bits are reserved or to beinterpreted as described in this embodiment), and 4-6 bits may be usedfor VRB to PRB mapping and MCS.

In certain embodiments, a new RNTI may be used to detect and distinguisha redesigned DCI format 1_0 from DCI format 1_0. In such embodiments,the “Legacy usage” bit described above may not be used.

In various embodiments, DCI carrying a PDCCH order may also carry thescheduling information for PDSCH carrying one or several DL TBs. In suchembodiments, a content of a DCI format for this DCI may be based onexisting DCI format 1_1, which supports scheduling more than 1 DL TB.

A new DCI format based on DCI format 1_1 may have contents of both PDCCHorder as well as downlink assignment. Some of the contents from format1_1 may be omitted to reduce the size of the new DCI format or to makeit the same size as and/or similar size to format 1_1. The content ofthis new DCI format may resemble the content as described herein.

In some embodiments, the contents of DCI format 1_1 may be redesigned orrearranged to include only information necessary at times in which bothPDCCH order and downlink assignment are present. In certain embodiments,a UE capability may indicate if the UE 502 is capable of interpretingthe redesigned format 1_1. Furthermore, if the network is capable oftransmitting a redesigned format 1_1, the network may indicate thiscapability to the UE 502 (e.g., using RRC signaling configuration). Forexample, the network may indicate that the DCI format 1_1 will be usedin a redesigned way.

In some embodiments, parsing and interpretation of a redesigned DCIformat 1_1 may be done as described herein. In various embodiments, thefollowing information may be transmitted using the redesigned DCI format1_1 with CRC scrambled by C-RNTI, CS-RNTI, or a new-RNTI: 1) Identifierfor DCI formats—1 bit. The value of this bit field is always set to 1,indicating a DL DCI format; 2) Legacy usage—1 bit. A value of TRUE meansthat the rest of the fields in this DCI will be interpreted exactly asin legacy DCI format 1_1 but starting immediately after the “Identifierfor DCI formats.” A value of FALSE means that the rest of the fields inthis DCI will be interpreted in a redesigned was as shown further: Asmay be appreciated, the use of TRUE and FALSE could be used oppositethat described herein. Moreover, this field may be renamed to “newusage,” “combined usage,” or any suitable name; 3) Frequency domainresource assignment—┌log₂(N_(RB) ^(DL,BWP)(N_(RB) ^(DL,BWP)+1)/2)┐ bits.N_(RB) ^(DL,BWP) is the size of the active DL bandwidth part in case DCIformat 1_1 is monitored in the UE specific search space and satisfying:the total number of different DCI sizes monitored per slot is no morethan 4 for the cell, and the total number of different DCI sizes withC-RNTI monitored per slot is no more than 3 for the cell, otherwise,N_(RB) ^(DL,BWP) is the size of the initial DL bandwidth part; 4) RandomAccess Preamble index—6 bits according to ra-PreambleIndex in Subclause5.1.2 of [8, TS38.321]; 5) UL/SUL indicator—1 bit. If the value of the“Random Access Preamble index” is not all zeros and, if the UE isconfigured with SUL in the cell, this field indicates which UL carrierin the cell to transmit the PRACH according to Table 7.3.1.1.1-1;otherwise, this field is reserved; 6) SS/PBCH index—6 bits. If the valueof the “Random Access Preamble index” is not all zeros, this fieldindicates the SS/PBCH that shall be used to determine the RACH occasionfor the PRACH transmission; otherwise, this field is reserved; 7) PRACHMask index—4 bits. If the value of the “Random Access Preamble index” isnot all zeros, this field indicates the RACH occasion associated withthe SS/PBCH indicated by “SS/PBCH index” for the PRACH transmission,according to Subclause 5.1.1 of [8, TS38.321]; otherwise, this field isreserved; 8) Time domain resource assignment—optionally present. A slotlocation for PDSCH may be fixed or RRC configured relative to a selectedPRACH occasion or relative to a slot where PDCCH order DCI istransmitted. If present, the network may indicate a starting symbolwithin a slot and PDSCH duration (in terms of # of symbols) depending onthe DL TB size. If not present, in one possible embodiment, the PRACHand DL assignment (i.e. PDSCH reception) take place at the same point intime (subframe, symbol#) or are apart from each other by a value (e.g.in number of symbols) either defined in specification or configured byhigher layer like RRC; 9) VRB-to-PRB mapping—1 bit according to Table7.3.1.1.2-33 of TS 38.212-f20; 10) Modulation and coding scheme—5 bitsas defined in Subclause 5.1.3 of [6, TS 38.214]; 11) New dataindicator—Not present; 12) Redundancy version—not present; 13) HARQprocess number—Not present. Instead, in one embodiment, a fixed HARQprocess ID is used which is known to both the network and the UE by wayof specification or configured by higher layer like RRC. If thisreserved/fixed HARQ process ID was being used already (when TAT isrunning at the time of receiving a PDCCH order) i.e., a non-empty HARQbuffer, then the HARQ buffer shall be overwritten with the contents ofthe DL TB; 14) Downlink assignment index—not present; 15) TPC commandfor scheduled PUCCH—not present; 16) PUCCH resource indicator—3 bits asdefined in Subclause 9.2.3 of [5, TS 38.213]—in one embodiment, this ispresent, in another embodiment, this is not present; 17) PDSCH-to-HARQfeedback timing indicator—if not present PUCCH feedback after the DL-SCHcould be based on fixed time location (e.g., offset). Otherwise, itcould be signaled explicitly as in format 1_0 for DL assignment.

In certain embodiments, a PDCCH order DCI format 1_0 as defined in 3GPPTS 38.212-f20 may be used in a redesigned way (e.g., the CRC of the DCIformat 1_0 may be scrambled by C-RNTI but the “Frequency domain resourceassignment” field may have valid resource signaling i.e., not all ones).In such embodiments, the 10 reserved bits of the PDCCH order may be usedso that one of these 10 reserved bits indicates whether the new or oldformat 1_0 applies (e.g., if the 10 reserved bits are reserved or to beinterpreted as in this embodiment) and 4-6 bits may be used for VRB toPRB mapping and MCS.

In one embodiment, the UE 502 may only interpret each field of the DCIformat 1_1 as described above if the uplink timing alignment timerexpires. In some embodiments, a new RNTI may be used to detect anddistinguish a redesigned DCI format 1_1 from DCI format 1_1. In suchembodiments, the “Legacy usage” bit described above may not be used.

In some embodiments, there may be two DCIs, both addressed to C-RNTI,sent to a UE capable of receiving both DCIs using the same C-RNTI. Insuch an embodiment, one of the DCIs carries a PDCCH order and the otherone carries scheduling information for a PDSCH carrying a DL TB. Incertain embodiments, the two DCIs may be sent together (e.g., in thesame subframe and/or symbol) or in subsequent time occasion withoutwaiting for the UE 502 to send feedback for the first DCI.

In various embodiments, if two DCIs are sued, a first DCI carrying aPDCCH order may be addressed to a new RNTI (e.g., a PDCCH-order-RNTI orPO-RNTI) and a second DCI carrying the scheduling information for thePDSCH carrying a DL TB may be addressed to C-RNTI. In such embodiments,the UE 502 may monitor only for PO-RNTI at times in which a TAT has notexpired (e.g., is still running), but may monitor for both the PO-RNTIand the C-RNTI if the TAT has expired. In such embodiments, the UE 502monitors both these RNTIs in the same (UE specific) search space.

In some embodiments, the HARQ feedback for a DL TB (and multiple DL TBsif applicable) is transmitted together with the PUSCH transmission forwhich the resources were allocated in RAR 518 (e.g., message 2).

In certain embodiments, the UE 502 includes a new MAC CE indicating HARQfeedback (e.g., ACK or NACK) for the DL TB (and multiple DL TBs ifapplicable) to the gNB 504. In such embodiments, if there is remaininggrant size (e.g., from message 2) it could be filled with data, padding,and/or a padding BSR. In some embodiments, a new MAC CE is a MAC controlelement identified using a reserved LCD and has the purpose ofindicating HARQ feedback (e.g., ACK or NACK) for the DL TB (and multipleDL TBs if applicable) to the gNB 502.

In various embodiments, at a physical layer, physical resources carryingPUSCH may also carry HARQ feedback for DL TB (and multiple DL TBs ifapplicable). In some embodiments, HARQ feedback may be multiplexed inPUSCH. In certain embodiments, CSI together with HARQ feedback may alsobe multiplexed in the PUSCH.

FIG. 6 is a schematic block diagram illustrating a further embodiment ofcommunications 600 between a UE 602 (e.g., remote unit 102) and a gNB604 (e.g., network unit 104). The communications 600 illustrate that theUE 602 starts in an RRC connected state 606. After TAT expiration 608,the UE 602 loses an UL synchronization 610. At a time after the UE 602loses the UL synchronization 610, DL data arrives 612 at the gNB 604. Inresponse to the DL data arriving 612 at the gNB 604, the gNB 604transmits 614 a PDCCH order to the UE 602. In this embodiment, the PDCCHorder transmitted 614 to the UE 602 may be transmitted with one or moreDL TBs based on the DL data that arrived 612 at the gNB 604. Afterreceiving the PDCCH order, the UE 602 initiates a PRACH procedure bytransmitting 616 a PRACH message 1 (e.g., PRACH preamble) to the gNB604. In this embodiment, feedback (e.g., HARQ-ACK, ACK/NACK) istransmitted with the PRACH message 1. In response to receiving the PRACHmessage 1, the gNB 604 transmits 618 a random access response (e.g.,message 2) to the UE 602. At a time 620 after the gNB 604 transmits 618the random access response, the UE 602 has UL synchronization.Accordingly, the UE 602 transmits a PUSCH 622 to the gNB 604. By usingthis set of communications 600, DL data (e.g., one or more DL TBs) maybe transmitted to the UE 602 faster than in other embodiments, such asthe embodiment described in FIG. 4.

In certain embodiments, the gNB 604 sends the DL TB along with the PDCCHorder and the UE 602 sends the HARQ feedback as part of the PRACHtransmission.

In various embodiments, the PDCCH order allocates two random accesspreambles. Both preambles may be reserved for the UE 602 until a certaintime. Therefore, the UE 602 may perform contention free random access attimes it uses one of these preambles immediately after having receivedthe PDCCH order. In certain embodiments, the PDCCH order indicates andreserves one of the two preambles (e.g., preamble-1) for a HARQ ACKfeedback. For example, the UE 602 may make the PRACH message 1transmission using preamble-1 in response to the UE 602 successfullydecoding the DL TB. Similarly, in some embodiments, the PDCCH orderindicates and reserves the other of the two preambles (e.g., preamble-2)for a HARQ NACK feedback. For example, the UE 602 may make the PRACHmessage 1 transmission using preamble-2 in response to the UE 602 notsuccessfully decoding the DL TB. As may be appreciated, the PRACHtransmission is described in 3GPP TS 38.321 and 36.321-f20.

In some embodiments, a network signals only one preamble (e.g. forsignifying ACK feedback) in a corresponding DCI format. In suchembodiments, the UE 602 may derive a second preamble using a rule withrespect to the signaled preamble. For example, a preamble for NACKfeedback may be an immediate next preamble from the signaled preamble oris a preamble that is a certain fixed offset away from the signaledpreamble.

In certain embodiments, to distinguish between a HARQ ACK and a HARQNACK, a network may determine which PRACH time-frequency physicalresources are used for the transmission. Some PRACH time-frequencyphysical resources may be reserved for HARQ ACK, while other PRACHtime-frequency physical resources are reserved for HARQ NACK. In suchembodiments, the reservation of PRACH time-frequency physical resourcesmay be done by DCI for PDCCH order or may be done in broadcast signalingsuch that PRACH time-frequency physical resources with a first index(e.g., index-1) are for HARQ ACK and PRACH time-frequency physicalresources with a second index (e.g., index-2) are for HARQ NACK. In someembodiments, the network may ensure that not more than 1 UE is sent thePDCCH order with a DL TB at any given time window (e.g., a time windowof 5 or 10 ms).

In various embodiments, segregation between two PRACH time-frequencyphysical resources may done using some rules used to distinguish HARQACK from HARQ NACK. For example, resources are each ‘x’ PRB wide and theresources for NACK start after a certain offset, while the resources forACK end. In some embodiments, ACK resources occur on even subframesand/or symbol numbers, while NACK resources occur on odd subframesand/or symbol numbers. In other embodiments, ACK resources occur on oddsubframes and/or symbol numbers, while NACK resources occur on evensubframes and/or symbol numbers.

FIG. 7 is a schematic block diagram illustrating yet another embodimentof communications 700 between a UE 702 (e.g., remote unit 102) and a gNB704 (e.g., network unit 104). The communications 700 illustrate that theUE 702 starts in an RRC connected state 706. After TAT expiration 708,the UE 702 loses an UL synchronization 710. At a time after the UE 702loses the UL synchronization 710, DL data arrives 712 at the gNB 704. Inresponse to the DL data arriving 712 at the gNB 704, the gNB 704transmits 714 a PDCCH order to the UE 702. In this embodiment, the PDCCHorder transmitted 714 to the UE 702 may be transmitted with one or moreDL TBs based on the DL data that arrived 712 at the gNB 704. Afterreceiving the PDCCH order, in one embodiment, the UE 702 may transmit716 feedback (e.g., HARQ-ACK, ACK/NACK) in PUCCH before ULsynchronization. Moreover, the UE 702 initiates a PRACH procedure bytransmitting 718 a PRACH message 1 (e.g., PRACH preamble) to the gNB704. In response to receiving the PRACH message 1, the gNB 704 transmits720 a random access response (e.g., message 2) to the UE 702. At a time722 after the gNB 704 transmits 720 the random access response, the UE702 has UL synchronization. Accordingly, the UE 702 transmits a PUCCH724 to the gNB 704. In some embodiments, the feedback may be transmittedwith the PUCCH, after UL synchronization. By using this set ofcommunications 700, DL data (e.g., one or more DL TBs) may betransmitted to the UE 702 faster than in other embodiments, such as theembodiment described in FIG. 4.

In some embodiments, the gNB 704 sends one or more DL TBs along with thePDCCH order and the UE 702 sends the HARQ feedback on PUCCH. In variousembodiments, a new PUCCH may be used. The new PUCCH may have a longercyclic prefix length.

In various embodiments, one or more DL TBs may contain an RRCreconfiguration message and may also contain downlink data. In suchembodiments, PUCCH resources may be configured and/or reconfigured withthe RRC reconfiguration message. Moreover, the UE 702 may use theconfigured and/or reconfigured PUCCH resources to send HARQ feedbackeither: immediately (e.g., transmission 716, before getting ULSynchronized, such as if a serving cell is a small cell and a timingadvance “TA” is close to a zero value and/or the UE 702 may continue touse the NTA value—the NTA value may refer to an UL timing advance valuethat a UE has stored most recently); or afterwards (e.g., PUCCH 724).These same transmission instances may be used for sending HARQ feedbackfor re-transmissions. In certain embodiments, the network may indicatethat the same PUCCH configuration may be considered valid and/or activeas those that were configured previously before the UE 702 went out ofUL synchronization.

In some embodiments, PUCCH resources are used as defined in Chapter9.2.1 (e.g., PUCCH resource sets) of 3GPP TS 38.213-f20: “If a UE doesnot have dedicated PUCCH resource configuration, provided by higherlayer parameter PUCCH-ResourceSet in PUCCH-Config, a PUCCH resource setis provided by higher layer parameter pucch-ResourceCommon inSystemInformationBlockType1 through an index to a row of Table 9.2.1-1for transmission of HARQ-ACK information on PUCCH in an initial activeUL BWP of N_(BWP) ^(size) PRBs provided by SystemInformationBlockType1.”

In various embodiments, upon expiration of an uplink timing alignmenttimer, the UE 702 may release UE-specifically configured PUCCH resourcesof all serving cells associated with the corresponding timing advancegroup (“TAG”). Thus, in such embodiments, a PUCCH resource of acell-specifically configured PUCCH resource set may be used for HARQ-ACKtransmission. In other embodiments, the PUCCH resource set could bebased on one fixed index in a Table 9.2.1-1: of 38.213-f20 or, anapplicable index can be signaled in RRC (this may be UE specific).

In some embodiments, the UE 702 may use the PUCCH resources to send HARQfeedback immediately (e.g., before getting UL synchronized), or aftergetting UL synchronized, and for sending HARQ feedback forre-transmissions.

FIG. 8 is a schematic block diagram illustrating an additionalembodiment of communications 800 between a UE 802 (e.g., remote unit102) and a gNB 804 (e.g., network unit 104). The communications 800illustrate that the UE 802 starts in an RRC connected state 806. AfterTAT expiration 808, the UE 802 loses an UL synchronization 810. At atime after the UE 802 loses the UL synchronization 810, DL data arrives812 at the gNB 804. In response to the DL data arriving 812 at the gNB804, the gNB 804 transmits 814 a PDCCH order to the UE 802. Afterreceiving the PDCCH order, the UE 802 initiates a PRACH procedure bytransmitting 816 a PRACH message 1 (e.g., PRACH preamble) to the gNB804. In response to receiving the PRACH message 1, the gNB 804 transmits818 a random access response (e.g., message 2) to the UE 802. In thisembodiment, the random access response may be transmitted with one ormore DL TBs based on the DL data that arrived 812 at the gNB 804. At atime 820 after the gNB 804 transmits 820 the random access response, theUE 802 has UL synchronization. In this embodiment, the UE 802 maytransmit 822 feedback (e.g., HARQ-ACK, ACK/NACK) to the gNB 804 after ULsynchronization. By using this set of communications 800, DL data (e.g.,one or more DL TBs) may be transmitted to the UE 802 faster than inother embodiments, such as the embodiment described in FIG. 4.

In certain embodiments, the gNB 804 sends one or more DL TBs togetherwith the response (e.g., RAR, message 2) to UE's 802 message 1transmission using a dedicated preamble. However, the UE 802 sends thefeedback for the one or more DL TBs using any of the methods describedherein.

Combining the one or more DL TBs together with the response to UE's 802message 1 transmission may be done with the following options: 1) a newDCI format addressed to C-RNTI can be used with contents as follows: RANsends a DL assignment using (modified) DCI format 1_0 that also carriesthe UL TA value. Some of the contents of DCI format 1_0 as described inTS 38.212-f20 like new data indicator, redundancy version, HARQ processnumber, downlink assignment index, TPC command for scheduled PUCCH,PUCCH resource indicator etc. may be replaced with a timing advancecommand and/or an UL grant described as part of “MAC payload for RandomAccess Response” as described in Chapter 6.2.3 of TS 36.321-f20. The ULgrant may also be transmitted as part of the one or more DL TB; or 2) anew redesigned version of DCI format 1_0 as described herein may beused.

In various embodiments, the UE 802 receives a PDSCH including a timingadvance value, an UL grant, and a DL assignment for one or more DL TBsas payload and being scrambled based on C-RNTI (also correspondingscheduling PDCCH's CRC being scrambled with C-RNTI), in response to aPDCCH ordered PRACH preamble transmission being received by the gNB 804.In certain embodiments, message 2 PDSCH scrambled based on C-RNTI inresponse to the PDCCH ordered PRACH preamble transmission may include atiming advance value, an UL grant, and/or one or more DL TBs as payload.

In certain embodiments, the UE 802 monitors PDCCH with CRC scrambledwith C-RNTI for message 2 reception within a random access responsewindow, if the PDCCH ordered PRACH preamble transmission is performedand the uplink timing alignment timer expires.

FIG. 9 is a schematic block diagram illustrating yet a furtherembodiment of communications 900 between a UE 902 (e.g., remote unit102) and a gNB 904 (e.g., network unit 104). The communications 900illustrate that the UE 902 starts in an RRC connected state 906. AfterTAT expiration 908, the UE 902 loses an UL synchronization 910. At atime after the UE 902 loses the UL synchronization 910, DL data arrives912 at the gNB 904. In response to the DL data arriving 912 at the gNB904, the gNB 904 transmits 914 a PDCCH order to the UE 902. Afterreceiving the PDCCH order, in one embodiment, the UE 902 may transmit916 CSI feedback to the gNB 904.

In some embodiments, the gNB 904 includes a CSI request field along withthe PDCCH order (as described in TS 38.212-f20 Chapter 7.3.1.2.1) usingsome of the 10 reserved bits in the PDCCH order. In various embodiments,a CSI request is 0, 1, 2, 3, 4, 5, or 6 bits determined by a higherlayer parameter reportTriggerSize. In certain embodiments, the UE 902,upon receiving the PDCCH order with the CSI request field may initiate arandom access procedure, perform CSI estimation, and include the CSIestimation in a response to the gNB 904 similar to one of the feedbackresponses described herein.

In some embodiments, a DL TB is re-transmitted a fixed number of timeswhich the UE 904 may receive before the UE 902 is required to transmitany feedback. Feedback transmission may be accomplished using any of thefeedback responses described herein.

In certain embodiments, a DL TB may be re-transmitted a fixed number oftimes which the UE 902 may receive before the UE 902 is required totransmit any feedback. In various embodiments, feedback is transmittedonly if the UE 902 fails to decode the DL TB successfully. Feedbacktransmission may be accomplished using any of the feedback responsesdescribed herein.

In some embodiments, more than one DL TB may be transmitted with and/orafter a PDCCH order until the UE 902 starts to transmit a PRACH message1 or until the UE 902 receives message 2. If more than one DL TB istransmitted, then the RAN may indicate a HARQ process identifier.

In various embodiments, a network may indicate with a given DL TB thatthe DL TB is the last TB to be sent at that point of time. Thisindication may be sent along with a PDCCH order (as described in TS38.212-f20 Chapter 7.3.1.2.1) using one of the 10 reserved bits in thePDCCH order as a Boolean Flag (e.g., TRUE=Last DL TB). In certainembodiments, the UE 902 may: not perform any UL transmission afterreceiving this last DL TB; may transmit the feedback for this last DL TB(feedback transmission may be accomplished using any of the feedbackresponses described herein); and/or may just perform PRACH transmission,apply TA upon receiving the message 2 and transmit the feedback for thelast DL TB (feedback transmission may be accomplished using any of thefeedback responses described herein).

FIG. 10 is a flow chart diagram illustrating one embodiment of a method1000 for transmitting a physical downlink shared channel after losinguplink synchronization. In some embodiments, the method 1000 isperformed by an apparatus, such as the network unit 104. In certainembodiments, the method 1000 may be performed by a processor executingprogram code, for example, a microcontroller, a microprocessor, a CPU, aGPU, an auxiliary processing unit, a FPGA, or the like.

The method 1000 may include transmitting 1002 first downlink controlinformation that schedules a physical downlink control channel order. Insome embodiments, the method 1000 includes transmitting 1004 seconddownlink control information that schedules a physical downlink sharedchannel transmission. In certain embodiments, the method 1000 includestransmitting 1006 the physical downlink control channel order based onthe first downlink control information. In various embodiments, themethod 1000 includes transmitting 1008 the physical downlink sharedchannel transmission based on the second downlink control information.In such embodiments, the physical downlink control channel order and atleast a portion of the physical downlink shared channel transmission aretransmitted after a remote unit 102 loses an uplink synchronization andbefore the remote unit 102 completes a physical random access channelprocedure.

In various embodiments, the first downlink control information and thesecond downlink control information are carried within a same downlinkcontrol information format. In some embodiments, a field of the samedownlink control information format indicates the physical downlinkshared channel transmission. In certain embodiments, a reserved portionof the same downlink control information format indicates schedulinginformation for the physical downlink shared channel transmission.

In one embodiment, a reserved portion of the same downlink controlinformation format indicates a channel state information request. Invarious embodiments, a radio network temporary identifier indicateswhether the same downlink control information format comprises thesecond downlink control information. In some embodiments, the physicaldownlink shared channel transmission comprises only one transport block.

In certain embodiments, the physical downlink shared channeltransmission comprises a plurality of transport blocks. In oneembodiment, the first downlink control information and the seconddownlink control information are part of separate downlink controlinformation transmissions, and the remote unit 102 is configured todetect the separate downlink control information transmissions. Invarious embodiments, the separate downlink control informationtransmissions are both addressed to a same radio network temporaryidentifier. In some embodiments, the separate downlink controlinformation transmissions are addressed to different radio networktemporary identifiers.

FIG. 11 is a flow chart diagram illustrating one embodiment of a method1100 for receiving a physical downlink shared channel after losinguplink synchronization. In some embodiments, the method 1100 isperformed by an apparatus, such as the remote unit 102. In certainembodiments, the method 1100 may be performed by a processor executingprogram code, for example, a microcontroller, a microprocessor, a CPU, aGPU, an auxiliary processing unit, a FPGA, or the like.

The method 1100 may include receiving 1102 first downlink controlinformation that schedules a physical downlink control channel order. Insome embodiments, the method 1100 includes receiving 1104 seconddownlink control information that schedules a physical downlink sharedchannel transmission. In certain embodiments, the method 1100 includesreceiving 1106 the physical downlink control channel order based on thefirst downlink control information. In various embodiments, the method1100 includes receiving 1108 the physical downlink shared channeltransmission based on the second downlink control information. In suchembodiments, the physical downlink control channel order and at least aportion of the physical downlink shared channel transmission arereceived after a remote unit 102 loses an uplink synchronization andbefore the remote unit 102 completes a physical random access channelprocedure.

In various embodiments, the first downlink control information and thesecond downlink control information are carried within a same downlinkcontrol information format. In some embodiments, a field of the samedownlink control information format indicates the physical downlinkshared channel transmission. In certain embodiments, a reserved portionof the same downlink control information format indicates schedulinginformation for the physical downlink shared channel transmission.

In one embodiment, a reserved portion of the same downlink controlinformation format indicates a channel state information request. Invarious embodiments, a radio network temporary identifier indicateswhether the same downlink control information format comprises thesecond downlink control information. In some embodiments, the physicaldownlink shared channel transmission comprises only one transport block.

In certain embodiments, the physical downlink shared channeltransmission comprises a plurality of transport blocks. In oneembodiment, the first downlink control information and the seconddownlink control information are part of separate downlink controlinformation transmissions, and the remote unit 102 is configured todetect the separate downlink control information transmissions. Invarious embodiments, the separate downlink control informationtransmissions are both addressed to a same radio network temporaryidentifier. In some embodiments, the separate downlink controlinformation transmissions are addressed to different radio networktemporary identifiers.

FIG. 12 is a flow chart diagram illustrating another embodiment of amethod 1200 for transmitting a physical downlink shared channel afterlosing uplink synchronization. In some embodiments, the method 1200 isperformed by an apparatus, such as the network unit 104. In certainembodiments, the method 1200 may be performed by a processor executingprogram code, for example, a microcontroller, a microprocessor, a CPU, aGPU, an auxiliary processing unit, a FPGA, or the like.

The method 1200 may include transmitting 1202 a physical downlinkcontrol channel order. In some embodiments, the method 1200 includestransmitting 1204 a physical downlink shared channel transmission. Insuch embodiments, the physical downlink control channel order and atleast a portion of the physical downlink shared channel transmission aretransmitted after a remote unit 102 loses an uplink synchronization andbefore the remote unit 102 completes a physical random access channelprocedure. In certain embodiments, the method 1200 includes receiving1206 feedback information corresponding to the physical downlink sharedchannel transmission.

In various embodiments, the feedback information is received usingresources allocated by a random access response. In some embodiments,the feedback information is received using a medium access controlcontrol element. In certain embodiments, the feedback information ismultiplexed with a physical uplink shared channel transmission.

In one embodiment, the feedback information is received as part of aphysical random access channel transmission. In various embodiments, thefeedback information is received by a first random access channelpreamble indicating an acknowledgement and a second random accesschannel preamble indicating a non-acknowledgement. In some embodiments,the method 1200 comprises transmitting information indicating the firstrandom access channel preamble and the second random access channelpreamble.

In certain embodiments, the method 1200 comprises transmittinginformation indicating either the first random access channel preambleor the second random access channel preamble, wherein the remote unit102 comprises a mapping linking the first random access channel preambleto the second random access channel preamble. In one embodiment, thefeedback information is received by a first set of resources indicatingan acknowledgement and a second set of resources indicating anon-acknowledgement. In various embodiments, predetermined rules areused to identify the first set of resources and the second set ofresources.

In some embodiments, the feedback information is received usingresources allocated by a radio resource control message. In certainembodiments, the feedback information is received using physical uplinkcontrol channel resources. In one embodiment, transmitting the physicaldownlink shared channel transmission comprises transmitting the physicaldownlink shared channel transmission a predetermined number of times.

In various embodiments, receiving the feedback information comprisesreceiving the feedback information after the physical downlink sharedchannel transmission is transmitted the predetermined number of times.In some embodiments, receiving the feedback information comprisesreceiving the feedback information only in response to the remote unit102 failing to decode the physical downlink shared channel transmission.In certain embodiments, transmitting the physical downlink sharedchannel transmission comprises transmitting a plurality of transportblocks, and receiving the feedback information comprises receiving ahybrid automatic repeat request identity for each transport block of theplurality of transport blocks. In one embodiment, transmitting theplurality of transport blocks comprises transmitting an indication witha last transport block of the plurality of transport blocks, and theindication indicates that no transport blocks are to be transmittedafter the last transport block.

FIG. 13 is a flow chart diagram illustrating another embodiment of amethod 1300 for receiving a physical downlink shared channel afterlosing uplink synchronization. In some embodiments, the method 1300 isperformed by an apparatus, such as the remote unit 102. In certainembodiments, the method 1300 may be performed by a processor executingprogram code, for example, a microcontroller, a microprocessor, a CPU, aGPU, an auxiliary processing unit, a FPGA, or the like.

The method 1300 may include receiving 1302 a physical downlink controlchannel order. In some embodiments, the method 1300 includes receiving1304 a physical downlink shared channel transmission. In suchembodiments, the physical downlink control channel order and at least aportion of the physical downlink shared channel transmission arereceived after a remote unit 102 loses an uplink synchronization andbefore the remote unit 102 completes a physical random access channelprocedure. In certain embodiments, the method 1300 includes transmitting1306 feedback information corresponding to the physical downlink sharedchannel transmission.

In various embodiments, the feedback information is transmitted usingresources allocated by a random access response. In some embodiments,the feedback information is transmitted using a medium access controlcontrol element. In certain embodiments, the feedback information ismultiplexed with a physical uplink shared channel transmission.

In one embodiment, the feedback information is transmitted as part of aphysical random access channel transmission. In various embodiments, thefeedback information is transmitted by a first random access channelpreamble indicating an acknowledgement and a second random accesschannel preamble indicating a non-acknowledgement. In some embodiments,the method 1300 comprises receiving information indicating the firstrandom access channel preamble and the second random access channelpreamble.

In certain embodiments, the method 1300 comprises receiving informationindicating either the first random access channel preamble or the secondrandom access channel preamble, wherein the remote unit 102 comprises amapping linking the first random access channel preamble to the secondrandom access channel preamble. In one embodiment, the feedbackinformation is transmitted by a first set of resources indicating anacknowledgement and a second set of resources indicating anon-acknowledgement. In various embodiments, predetermined rules areused to identify the first set of resources and the second set ofresources.

In some embodiments, the feedback information is transmitted usingresources allocated by a radio resource control message. In certainembodiments, the feedback information is transmitted using physicaluplink control channel resources. In one embodiment, receiving thephysical downlink shared channel transmission comprises receiving thephysical downlink shared channel transmission a predetermined number oftimes. In various embodiments, transmitting the feedback informationcomprises transmitting the feedback information after the physicaldownlink shared channel transmission is received the predeterminednumber of times.

In some embodiments, transmitting the feedback information comprisestransmitting the feedback information only in response to the remoteunit 102 failing to decode the physical downlink shared channeltransmission. In certain embodiments, receiving the physical downlinkshared channel transmission comprises receiving a plurality of transportblocks, and transmitting the feedback information comprises transmittinga hybrid automatic repeat request identity for each transport block ofthe plurality of transport blocks. In one embodiment, receiving theplurality of transport blocks comprises receiving an indication with alast transport block of the plurality of transport blocks, and theindication indicates that no transport blocks are to be received afterthe last transport block.

FIG. 14 is a flow chart diagram illustrating one embodiment of a method1400 for transmitting downlink data. In some embodiments, the method1400 is performed by an apparatus, such as the network unit 104. Incertain embodiments, the method 1400 may be performed by a processorexecuting program code, for example, a microcontroller, amicroprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, orthe like.

The method 1400 may include determining 1402 a remote unit 102 that isto receive downlink data. In some embodiments, the method 1400 includestransmitting 1404 the downlink data with a random access response. Insuch embodiments, the downlink data is transmitted after the remote unit102 loses an uplink synchronization and before the remote unit 102completes a physical random access channel procedure. In certainembodiments, the method 1400 includes receiving 1406 feedbackinformation corresponding to the downlink data.

In various embodiments, the method 1400 comprises receiving a physicalrandom access channel preamble from the remote unit 102, whereindetermining the remote unit 102 that is to receive downlink datacomprises determining the remote unit 102 based on the physical randomaccess channel preamble received from the remote unit 102. In someembodiments, the method 1400 comprises transmitting informationindicating the physical random access channel preamble to the remoteunit 102. In certain embodiments, the method 1400 comprises receiving aphysical random access channel preamble from the remote unit 102,wherein determining the remote unit 102 that is to receive downlink datacomprises determining the remote unit 102 based on resources carryingthe physical random access channel preamble.

In one embodiment, the method 1400 comprises transmitting informationindicating the resources to the remote unit 102. In various embodiments,the method 1400 comprises receiving information identifying the remoteunit 102, wherein determining the remote unit 102 that is to receivedownlink data comprises determining the remote unit 102 based on theinformation identifying the remote unit 102. In some embodiments, theinformation identifying the remote unit 102 is transmitted with aphysical random access channel preamble.

In certain embodiments, determining the remote unit 102 that is toreceive downlink data comprises determining the remote unit 102 based onresources used to receive a message from the remote unit 102. In oneembodiment, the method 1400 comprises transmitting informationallocating the resources to the remote unit 102. In various embodiments,the method 1400 comprises transmitting a downlink control informationformat to the remote unit 102.

In some embodiments, information in the downlink control informationformat indicates an uplink timing advance value and downlink assignmentfor the downlink data. In certain embodiments, the downlink controlinformation format is addressed to the remote unit 102. In oneembodiment, the method 1400 comprises transmitting a physical downlinkshared channel transmission to the remote unit 102 that indicates anuplink timing advance value and downlink assignment for the downlinkdata. In various embodiments, the physical downlink shared channeltransmission is scrambled based on a radio network temporary identifier.

FIG. 15 is a flow chart diagram illustrating one embodiment of a method1500 for receiving downlink data. In some embodiments, the method 1500is performed by an apparatus, such as the remote unit 102. In certainembodiments, the method 1500 may be performed by a processor executingprogram code, for example, a microcontroller, a microprocessor, a CPU, aGPU, an auxiliary processing unit, a FPGA, or the like.

The method 1500 may include receiving 1502 downlink data with a randomaccess response. In such embodiments, the downlink data is receivedafter a remote unit 102 loses an uplink synchronization and before theremote unit 102 completes a physical random access channel procedure. Insome embodiments, the method 1500 includes transmitting 1504 feedbackinformation corresponding to the downlink data.

In various embodiments, the method 1500 comprises receiving informationfrom a network unit 104 indicating a physical random access channelpreamble. In some embodiments, the method 1500 comprises transmittingthe physical random access channel preamble to the network unit 104. Incertain embodiments, the method 1500 comprises receiving informationindicating resources for carrying a physical random access channelpreamble.

In one embodiment, the method 1500 comprises transmitting the physicalrandom access channel preamble using the resources. In variousembodiments, the method 1500 comprises transmitting informationidentifying the remote unit 102 with a physical random access channelpreamble. In some embodiments, the method 1500 comprises receivinginformation allocating resources to the remote unit 102.

In certain embodiments, the method 1500 comprises transmitting a messageto a network unit 104 using the allocated resources. In one embodiment,the method 1500 comprises receiving a downlink control informationformat from a network unit 104. In various embodiments, information inthe downlink control information format indicates an uplink timingadvance value and downlink assignment for the downlink data.

In some embodiments, the downlink control information format isaddressed to the remote unit 102. In certain embodiments, the method1500 comprises receiving a physical downlink shared channel transmissionfrom a network unit 104 that indicates an uplink timing advance valueand downlink assignment for the downlink data. In one embodiment, thephysical downlink shared channel transmission is scrambled based on aradio network temporary identifier.

In one embodiment, a method comprises: transmitting first downlinkcontrol information that schedules a physical downlink control channelorder; transmitting second downlink control information that schedules aphysical downlink shared channel transmission; transmitting the physicaldownlink control channel order based on the first downlink controlinformation; and transmitting the physical downlink shared channeltransmission based on the second downlink control information, whereinthe physical downlink control channel order and at least a portion ofthe physical downlink shared channel transmission are transmitted aftera remote unit loses an uplink synchronization and before the remote unitcompletes a physical random access channel procedure.

In various embodiments, the first downlink control information and thesecond downlink control information are carried within a same downlinkcontrol information format.

In some embodiments, a field of the same downlink control informationformat indicates the physical downlink shared channel transmission.

In certain embodiments, a reserved portion of the same downlink controlinformation format indicates scheduling information for the physicaldownlink shared channel transmission.

In one embodiment, a reserved portion of the same downlink controlinformation format indicates a channel state information request.

In various embodiments, a radio network temporary identifier indicateswhether the same downlink control information format comprises thesecond downlink control information.

In some embodiments, the physical downlink shared channel transmissioncomprises only one transport block.

In certain embodiments, the physical downlink shared channeltransmission comprises a plurality of transport blocks.

In one embodiment, the first downlink control information and the seconddownlink control information are part of separate downlink controlinformation transmissions, and the remote unit is configured to detectthe separate downlink control information transmissions.

In various embodiments, the separate downlink control informationtransmissions are both addressed to a same radio network temporaryidentifier.

In some embodiments, the separate downlink control informationtransmissions are addressed to different radio network temporaryidentifiers.

In one embodiment, an apparatus comprises: a transmitter that: transmitsfirst downlink control information that schedules a physical downlinkcontrol channel order; transmits second downlink control informationthat schedules a physical downlink shared channel transmission;transmits the physical downlink control channel order based on the firstdownlink control information; and transmits the physical downlink sharedchannel transmission based on the second downlink control information,wherein the physical downlink control channel order and at least aportion of the physical downlink shared channel transmission aretransmitted after a remote unit loses an uplink synchronization andbefore the remote unit completes a physical random access channelprocedure.

In various embodiments, the first downlink control information and thesecond downlink control information are carried within a same downlinkcontrol information format.

In some embodiments, a field of the same downlink control informationformat indicates the physical downlink shared channel transmission.

In certain embodiments, a reserved portion of the same downlink controlinformation format indicates scheduling information for the physicaldownlink shared channel transmission.

In one embodiment, a reserved portion of the same downlink controlinformation format indicates a channel state information request.

In various embodiments, a radio network temporary identifier indicateswhether the same downlink control information format comprises thesecond downlink control information.

In some embodiments, the physical downlink shared channel transmissioncomprises only one transport block.

In certain embodiments, the physical downlink shared channeltransmission comprises a plurality of transport blocks.

In one embodiment, the first downlink control information and the seconddownlink control information are part of separate downlink controlinformation transmissions, and the remote unit is configured to detectthe separate downlink control information transmissions.

In various embodiments, the separate downlink control informationtransmissions are both addressed to a same radio network temporaryidentifier.

In some embodiments, the separate downlink control informationtransmissions are addressed to different radio network temporaryidentifiers.

In one embodiment, a method comprises: receiving first downlink controlinformation that schedules a physical downlink control channel order;receiving second downlink control information that schedules a physicaldownlink shared channel transmission; receiving the physical downlinkcontrol channel order based on the first downlink control information;and receiving the physical downlink shared channel transmission based onthe second downlink control information, wherein the physical downlinkcontrol channel order and at least a portion of the physical downlinkshared channel transmission are received after a remote unit loses anuplink synchronization and before the remote unit completes a physicalrandom access channel procedure.

In various embodiments, the first downlink control information and thesecond downlink control information are carried within a same downlinkcontrol information format.

In some embodiments, a field of the same downlink control informationformat indicates the physical downlink shared channel transmission.

In certain embodiments, a reserved portion of the same downlink controlinformation format indicates scheduling information for the physicaldownlink shared channel transmission.

In one embodiment, a reserved portion of the same downlink controlinformation format indicates a channel state information request.

In various embodiments, a radio network temporary identifier indicateswhether the same downlink control information format comprises thesecond downlink control information.

In some embodiments, the physical downlink shared channel transmissioncomprises only one transport block.

In certain embodiments, the physical downlink shared channeltransmission comprises a plurality of transport blocks.

In one embodiment, the first downlink control information and the seconddownlink control information are part of separate downlink controlinformation transmissions, and the remote unit is configured to detectthe separate downlink control information transmissions.

In various embodiments, the separate downlink control informationtransmissions are both addressed to a same radio network temporaryidentifier.

In some embodiments, the separate downlink control informationtransmissions are addressed to different radio network temporaryidentifiers.

In one embodiment, an apparatus comprises: a receiver that: receivesfirst downlink control information that schedules a physical downlinkcontrol channel order; receives second downlink control information thatschedules a physical downlink shared channel transmission; receives thephysical downlink control channel order based on the first downlinkcontrol information; and receives the physical downlink shared channeltransmission based on the second downlink control information, whereinthe physical downlink control channel order and at least a portion ofthe physical downlink shared channel transmission are received after aremote unit loses an uplink synchronization and before the remote unitcompletes a physical random access channel procedure.

In various embodiments, the first downlink control information and thesecond downlink control information are carried within a same downlinkcontrol information format.

In some embodiments, a field of the same downlink control informationformat indicates the physical downlink shared channel transmission.

In certain embodiments, a reserved portion of the same downlink controlinformation format indicates scheduling information for the physicaldownlink shared channel transmission.

In one embodiment, a reserved portion of the same downlink controlinformation format indicates a channel state information request.

In various embodiments, a radio network temporary identifier indicateswhether the same downlink control information format comprises thesecond downlink control information.

In some embodiments, the physical downlink shared channel transmissioncomprises only one transport block.

In certain embodiments, the physical downlink shared channeltransmission comprises a plurality of transport blocks.

In one embodiment, the first downlink control information and the seconddownlink control information are part of separate downlink controlinformation transmissions, and the remote unit is configured to detectthe separate downlink control information transmissions.

In various embodiments, the separate downlink control informationtransmissions are both addressed to a same radio network temporaryidentifier.

In some embodiments, the separate downlink control informationtransmissions are addressed to different radio network temporaryidentifiers.

In one embodiment, a method comprises: transmitting a physical downlinkcontrol channel order; transmitting a physical downlink shared channeltransmission, wherein the physical downlink control channel order and atleast a portion of the physical downlink shared channel transmission aretransmitted after a remote unit loses an uplink synchronization andbefore the remote unit completes a physical random access channelprocedure; and receiving feedback information corresponding to thephysical downlink shared channel transmission.

In various embodiments, the feedback information is received usingresources allocated by a random access response.

In some embodiments, the feedback information is received using a mediumaccess control control element.

In certain embodiments, the feedback information is multiplexed with aphysical uplink shared channel transmission.

In one embodiment, the feedback information is received as part of aphysical random access channel transmission.

In various embodiments, the feedback information is received by a firstrandom access channel preamble indicating an acknowledgement and asecond random access channel preamble indicating a non-acknowledgement.

In some embodiments, the method comprises transmitting informationindicating the first random access channel preamble and the secondrandom access channel preamble.

In certain embodiments, the method comprises transmitting informationindicating either the first random access channel preamble or the secondrandom access channel preamble, wherein the remote unit comprises amapping linking the first random access channel preamble to the secondrandom access channel preamble.

In one embodiment, the feedback information is received by a first setof resources indicating an acknowledgement and a second set of resourcesindicating a non-acknowledgement.

In various embodiments, predetermined rules are used to identify thefirst set of resources and the second set of resources.

In some embodiments, the feedback information is received usingresources allocated by a radio resource control message.

In certain embodiments, the feedback information is received usingphysical uplink control channel resources.

In one embodiment, transmitting the physical downlink shared channeltransmission comprises transmitting the physical downlink shared channeltransmission a predetermined number of times.

In various embodiments, receiving the feedback information comprisesreceiving the feedback information after the physical downlink sharedchannel transmission is transmitted the predetermined number of times.

In some embodiments, receiving the feedback information comprisesreceiving the feedback information only in response to the remote unitfailing to decode the physical downlink shared channel transmission.

In certain embodiments, transmitting the physical downlink sharedchannel transmission comprises transmitting a plurality of transportblocks, and receiving the feedback information comprises receiving ahybrid automatic repeat request identity for each transport block of theplurality of transport blocks.

In one embodiment, transmitting the plurality of transport blockscomprises transmitting an indication with a last transport block of theplurality of transport blocks, and the indication indicates that notransport blocks are to be transmitted after the last transport block.

In one embodiment, an apparatus comprises: a transmitter that: transmitsa physical downlink control channel order; and transmits a physicaldownlink shared channel transmission, wherein the physical downlinkcontrol channel order and at least a portion of the physical downlinkshared channel transmission are transmitted after a remote unit loses anuplink synchronization and before the remote unit completes a physicalrandom access channel procedure; and a receiver that receives feedbackinformation corresponding to the physical downlink shared channeltransmission.

In various embodiments, the feedback information is received usingresources allocated by a random access response.

In some embodiments, the feedback information is received using a mediumaccess control control element.

In certain embodiments, the feedback information is multiplexed with aphysical uplink shared channel transmission.

In one embodiment, the feedback information is received as part of aphysical random access channel transmission.

In various embodiments, the feedback information is received by a firstrandom access channel preamble indicating an acknowledgement and asecond random access channel preamble indicating a non-acknowledgement.

In some embodiments, the transmitter transmits information indicatingthe first random access channel preamble and the second random accesschannel preamble.

In certain embodiments, the transmitter transmits information indicatingeither the first random access channel preamble or the second randomaccess channel preamble, and the remote unit comprises a mapping linkingthe first random access channel preamble to the second random accesschannel preamble.

In one embodiment, the feedback information is received by a first setof resources indicating an acknowledgement and a second set of resourcesindicating a non-acknowledgement.

In various embodiments, predetermined rules are used to identify thefirst set of resources and the second set of resources.

In some embodiments, the feedback information is received usingresources allocated by a radio resource control message.

In certain embodiments, the feedback information is received usingphysical uplink control channel resources.

In one embodiment, the transmitter transmits the physical downlinkshared channel transmission by transmitting the physical downlink sharedchannel transmission a predetermined number of times.

In various embodiments, the receiver receives the feedback informationby receiving the feedback information after the physical downlink sharedchannel transmission is transmitted the predetermined number of times.

In some embodiments, the receiver receives the feedback information byreceiving the feedback information only in response to the remote unitfailing to decode the physical downlink shared channel transmission.

In certain embodiments, the transmitter transmits the physical downlinkshared channel transmission by transmitting a plurality of transportblocks, and the receiver receives the feedback information by receivinga hybrid automatic repeat request identity for each transport block ofthe plurality of transport blocks.

In one embodiment, the transmitter transmits the plurality of transportblocks by transmitting an indication with a last transport block of theplurality of transport blocks, and the indication indicates that notransport blocks are to be transmitted after the last transport block.

In one embodiment, a method comprises: receiving a physical downlinkcontrol channel order; receiving a physical downlink shared channeltransmission, wherein the physical downlink control channel order and atleast a portion of the physical downlink shared channel transmission arereceived after a remote unit loses an uplink synchronization and beforethe remote unit completes a physical random access channel procedure;and transmitting feedback information corresponding to the physicaldownlink shared channel transmission.

In various embodiments, the feedback information is transmitted usingresources allocated by a random access response.

In some embodiments, the feedback information is transmitted using amedium access control control element.

In certain embodiments, the feedback information is multiplexed with aphysical uplink shared channel transmission.

In one embodiment, the feedback information is transmitted as part of aphysical random access channel transmission.

In various embodiments, the feedback information is transmitted by afirst random access channel preamble indicating an acknowledgement and asecond random access channel preamble indicating a non-acknowledgement.

In some embodiments, the method comprises receiving informationindicating the first random access channel preamble and the secondrandom access channel preamble.

In certain embodiments, the method comprises receiving informationindicating either the first random access channel preamble or the secondrandom access channel preamble, wherein the remote unit comprises amapping linking the first random access channel preamble to the secondrandom access channel preamble.

In one embodiment, the feedback information is transmitted by a firstset of resources indicating an acknowledgement and a second set ofresources indicating a non-acknowledgement.

In various embodiments, predetermined rules are used to identify thefirst set of resources and the second set of resources.

In some embodiments, the feedback information is transmitted usingresources allocated by a radio resource control message.

In certain embodiments, the feedback information is transmitted usingphysical uplink control channel resources.

In one embodiment, receiving the physical downlink shared channeltransmission comprises receiving the physical downlink shared channeltransmission a predetermined number of times.

In various embodiments, transmitting the feedback information comprisestransmitting the feedback information after the physical downlink sharedchannel transmission is received the predetermined number of times.

In some embodiments, transmitting the feedback information comprisestransmitting the feedback information only in response to the remoteunit failing to decode the physical downlink shared channeltransmission.

In certain embodiments, receiving the physical downlink shared channeltransmission comprises receiving a plurality of transport blocks, andtransmitting the feedback information comprises transmitting a hybridautomatic repeat request identity for each transport block of theplurality of transport blocks.

In one embodiment, receiving the plurality of transport blocks comprisesreceiving an indication with a last transport block of the plurality oftransport blocks, and the indication indicates that no transport blocksare to be received after the last transport block.

In one embodiment, an apparatus comprises: a receiver that: receives aphysical downlink control channel order; and receives a physicaldownlink shared channel transmission, wherein the physical downlinkcontrol channel order and at least a portion of the physical downlinkshared channel transmission are received after a remote unit loses anuplink synchronization and before the remote unit completes a physicalrandom access channel procedure; and a transmitter that transmitsfeedback information corresponding to the physical downlink sharedchannel transmission.

In various embodiments, the feedback information is transmitted usingresources allocated by a random access response.

In some embodiments, the feedback information is transmitted using amedium access control control element.

In certain embodiments, the feedback information is multiplexed with aphysical uplink shared channel transmission.

In one embodiment, the feedback information is transmitted as part of aphysical random access channel transmission.

In various embodiments, the feedback information is transmitted by afirst random access channel preamble indicating an acknowledgement and asecond random access channel preamble indicating a non-acknowledgement.

In some embodiments, the receiver receives information indicating thefirst random access channel preamble and the second random accesschannel preamble.

In certain embodiments, the receiver receives information indicatingeither the first random access channel preamble or the second randomaccess channel preamble, and the remote unit comprises a mapping linkingthe first random access channel preamble to the second random accesschannel preamble.

In one embodiment, the feedback information is transmitted by a firstset of resources indicating an acknowledgement and a second set ofresources indicating a non-acknowledgement.

In various embodiments, predetermined rules are used to identify thefirst set of resources and the second set of resources.

In some embodiments, the feedback information is transmitted usingresources allocated by a radio resource control message.

In certain embodiments, the feedback information is transmitted usingphysical uplink control channel resources.

In one embodiment, the receiver receives the physical downlink sharedchannel transmission by receiving the physical downlink shared channeltransmission a predetermined number of times.

In various embodiments, the transmitter transmits the feedbackinformation by transmitting the feedback information after the physicaldownlink shared channel transmission is received the predeterminednumber of times.

In some embodiments, the transmitter transmits the feedback informationby transmitting the feedback information only in response to the remoteunit failing to decode the physical downlink shared channeltransmission.

In certain embodiments, the receiver receives the physical downlinkshared channel transmission by receiving a plurality of transportblocks, and the transmitter transmits the feedback information bytransmitting a hybrid automatic repeat request identity for eachtransport block of the plurality of transport blocks.

In one embodiment, the receiver receives the plurality of transportblocks by receiving an indication with a last transport block of theplurality of transport blocks, and the indication indicates that notransport blocks are to be received after the last transport block.

In one embodiment, a method comprises: determining a remote unit that isto receive downlink data; transmitting the downlink data with a randomaccess response, wherein the downlink data is transmitted after theremote unit loses an uplink synchronization and before the remote unitcompletes a physical random access channel procedure; and receivingfeedback information corresponding to the downlink data.

In various embodiments, the method comprises receiving a physical randomaccess channel preamble from the remote unit, wherein determining theremote unit that is to receive downlink data comprises determining theremote unit based on the physical random access channel preamblereceived from the remote unit.

In some embodiments, the method comprises transmitting informationindicating the physical random access channel preamble to the remoteunit.

In certain embodiments, the method comprises receiving a physical randomaccess channel preamble from the remote unit, wherein determining theremote unit that is to receive downlink data comprises determining theremote unit based on resources carrying the physical random accesschannel preamble.

In one embodiment, the method comprises transmitting informationindicating the resources to the remote unit.

In various embodiments, the method comprises receiving informationidentifying the remote unit, wherein determining the remote unit that isto receive downlink data comprises determining the remote unit based onthe information identifying the remote unit.

In some embodiments, the information identifying the remote unit istransmitted with a physical random access channel preamble.

In certain embodiments, determining the remote unit that is to receivedownlink data comprises determining the remote unit based on resourcesused to receive a message from the remote unit.

In one embodiment, the method comprises transmitting informationallocating the resources to the remote unit.

In various embodiments, the method comprises transmitting a downlinkcontrol information format to the remote unit.

In some embodiments, information in the downlink control informationformat indicates an uplink timing advance value and downlink assignmentfor the downlink data.

In certain embodiments, the downlink control information format isaddressed to the remote unit.

In one embodiment, the method comprises transmitting a physical downlinkshared channel transmission to the remote unit that indicates an uplinktiming advance value and downlink assignment for the downlink data.

In various embodiments, the physical downlink shared channeltransmission is scrambled based on a radio network temporary identifier.

In one embodiment, an apparatus comprises: a processor that determines aremote unit that is to receive downlink data; a transmitter thattransmits the downlink data with a random access response, wherein thedownlink data is transmitted after the remote unit loses an uplinksynchronization and before the remote unit completes a physical randomaccess channel procedure; and a receiver that receives feedbackinformation corresponding to the downlink data.

In various embodiments, the receiver receives a physical random accesschannel preamble from the remote unit, and the processor determines theremote unit that is to receive downlink data by determining the remoteunit based on the physical random access channel preamble received fromthe remote unit.

In some embodiments, the transmitter transmits information indicatingthe physical random access channel preamble to the remote unit.

In certain embodiments, the receiver receives a physical random accesschannel preamble from the remote unit, and the processor determines theremote unit that is to receive downlink data by determining the remoteunit based on resources carrying the physical random access channelpreamble.

In one embodiment, the transmitter transmits information indicating theresources to the remote unit.

In various embodiments, the receiver receives information identifyingthe remote unit, and the processor determines the remote unit that is toreceive downlink data by determining the remote unit based on theinformation identifying the remote unit.

In some embodiments, the information identifying the remote unit istransmitted with a physical random access channel preamble.

In certain embodiments, the processor determines the remote unit that isto receive downlink data by determining the remote unit based onresources used to receive a message from the remote unit.

In one embodiment, the transmitter transmits information allocating theresources to the remote unit.

In various embodiments, the transmitter transmits a downlink controlinformation format to the remote unit.

In some embodiments, information in the downlink control informationformat indicates an uplink timing advance value and downlink assignmentfor the downlink data.

In certain embodiments, the downlink control information format isaddressed to the remote unit.

In one embodiment, the transmitter transmits a physical downlink sharedchannel transmission to the remote unit that indicates an uplink timingadvance value and downlink assignment for the downlink data.

In various embodiments, the physical downlink shared channeltransmission is scrambled based on a radio network temporary identifier.

In one embodiment, a method comprises: receiving downlink data with arandom access response, wherein the downlink data is received after aremote unit loses an uplink synchronization and before the remote unitcompletes a physical random access channel procedure; and transmittingfeedback information corresponding to the downlink data.

In various embodiments, the method comprises receiving information froma network unit indicating a physical random access channel preamble.

In some embodiments, the method comprises transmitting the physicalrandom access channel preamble to the network unit.

In certain embodiments, the method comprises receiving informationindicating resources for carrying a physical random access channelpreamble.

In one embodiment, the method comprises transmitting the physical randomaccess channel preamble using the resources.

In various embodiments, the method comprises transmitting informationidentifying the remote unit with a physical random access channelpreamble.

In some embodiments, the method comprises receiving informationallocating resources to the remote unit.

In certain embodiments, the method comprises transmitting a message to anetwork unit using the allocated resources.

In one embodiment, the method comprises receiving a downlink controlinformation format from a network unit.

In various embodiments, information in the downlink control informationformat indicates an uplink timing advance value and downlink assignmentfor the downlink data.

In some embodiments, the downlink control information format isaddressed to the remote unit.

In certain embodiments, the method comprises receiving a physicaldownlink shared channel transmission from a network unit that indicatesan uplink timing advance value and downlink assignment for the downlinkdata.

In one embodiment, the physical downlink shared channel transmission isscrambled based on a radio network temporary identifier.

In one embodiment, an apparatus comprises: a receiver that receivesdownlink data with a random access response, wherein the downlink datais received after a remote unit loses an uplink synchronization andbefore the remote unit completes a physical random access channelprocedure; and a transmitter that transmits feedback informationcorresponding to the downlink data.

In various embodiments, the receiver receives information from a networkunit indicating a physical random access channel preamble.

In some embodiments, the transmitter transmits the physical randomaccess channel preamble to the network unit.

In certain embodiments, the receiver receives information indicatingresources for carrying a physical random access channel preamble.

In one embodiment, the transmitter transmits the physical random accesschannel preamble using the resources.

In various embodiments, the transmitter transmits informationidentifying the remote unit with a physical random access channelpreamble.

In some embodiments, the receiver receives information allocatingresources to the remote unit.

In certain embodiments, the transmitter transmits a message to a networkunit using the allocated resources.

In one embodiment, the receiver receives a downlink control informationformat from a network unit.

In various embodiments, information in the downlink control informationformat indicates an uplink timing advance value and downlink assignmentfor the downlink data.

In some embodiments, the downlink control information format isaddressed to the remote unit.

In certain embodiments, the receiver receives a physical downlink sharedchannel transmission from a network unit that indicates an uplink timingadvance value and downlink assignment for the downlink data.

In one embodiment, the physical downlink shared channel transmission isscrambled based on a radio network temporary identifier.

Embodiments may be practiced in other specific forms. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

1. A method comprising: transmitting first downlink control informationthat schedules a physical downlink control channel order; transmittingsecond downlink control information that schedules a physical downlinkshared channel transmission; transmitting the physical downlink controlchannel order based on the first downlink control information; andtransmitting the physical downlink shared channel transmission based onthe second downlink control information, wherein the physical downlinkcontrol channel order and at least a portion of the physical downlinkshared channel transmission are transmitted after a remote unit loses anuplink synchronization and before the remote unit completes a physicalrandom access channel procedure.
 2. The method of claim 1, wherein thefirst downlink control information and the second downlink controlinformation are carried within a same downlink control informationformat.
 3. The method of claim 2, wherein a field of the same downlinkcontrol information format indicates the physical downlink sharedchannel transmission.
 4. The method of claim 2, wherein a reservedportion of the same downlink control information format indicatesscheduling information for the physical downlink shared channeltransmission.
 5. The method of claim 2, wherein a reserved portion ofthe same downlink control information format indicates a channel stateinformation request.
 6. The method of claim 2, wherein a radio networktemporary identifier indicates whether the same downlink controlinformation format comprises the second downlink control information. 7.The method of claim 1, wherein the physical downlink shared channeltransmission comprises only one transport block.
 8. The method of claim1, wherein the physical downlink shared channel transmission comprises aplurality of transport blocks.
 9. The method of claim 1, wherein thefirst downlink control information and the second downlink controlinformation are part of separate downlink control informationtransmissions, and the remote unit is configured to detect the separatedownlink control information transmissions.
 10. The method of claim 9,wherein the separate downlink control information transmissions are bothaddressed to a same radio network temporary identifier.
 11. The methodof claim 9, wherein the separate downlink control informationtransmissions are addressed to different radio network temporaryidentifiers.
 12. An apparatus comprising: a transmitter that: transmitsfirst downlink control information that schedules a physical downlinkcontrol channel order; transmits second downlink control informationthat schedules a physical downlink shared channel transmission;transmits the physical downlink control channel order based on the firstdownlink control information; and transmits the physical downlink sharedchannel transmission based on the second downlink control information,wherein the physical downlink control channel order and at least aportion of the physical downlink shared channel transmission aretransmitted after a remote unit loses an uplink synchronization andbefore the remote unit completes a physical random access channelprocedure.
 13. A method comprising: receiving first downlink controlinformation that schedules a physical downlink control channel order;receiving second downlink control information that schedules a physicaldownlink shared channel transmission; receiving the physical downlinkcontrol channel order based on the first downlink control information;and receiving the physical downlink shared channel transmission based onthe second downlink control information, wherein the physical downlinkcontrol channel order and at least a portion of the physical downlinkshared channel transmission are received after a remote unit loses anuplink synchronization and before the remote unit completes a physicalrandom access channel procedure.
 14. The method of claim 13, wherein thefirst downlink control information and the second downlink controlinformation are carried within a same downlink control informationformat.
 15. The method of claim 14, wherein a field of the same downlinkcontrol information format indicates the physical downlink sharedchannel transmission.
 16. The method of claim 14, wherein a reservedportion of the same downlink control information format indicatesscheduling information for the physical downlink shared channeltransmission.
 17. The method of claim 14, wherein a radio networktemporary identifier indicates whether the same downlink controlinformation format comprises the second downlink control information.18. The method of claim 13, wherein the first downlink controlinformation and the second downlink control information are part ofseparate downlink control information transmissions, and the remote unitis configured to detect the separate downlink control informationtransmissions.
 19. The method of claim 18, wherein the separate downlinkcontrol information transmissions are both addressed to a same radionetwork temporary identifier.
 20. An apparatus comprising: a receiverthat: receives first downlink control information that schedules aphysical downlink control channel order; receives second downlinkcontrol information that schedules a physical downlink shared channeltransmission; receives the physical downlink control channel order basedon the first downlink control information; and receives the physicaldownlink shared channel transmission based on the second downlinkcontrol information, wherein the physical downlink control channel orderand at least a portion of the physical downlink shared channeltransmission are received after a remote unit loses an uplinksynchronization and before the remote unit completes a physical randomaccess channel procedure.